Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 24c4a791d1c5795392ee119dc7694f5cfb17b007ad6d45eafdcfbf5305542371

Tx prefix hash: a2664ea5be0a015543ffb7e94dcee0a924abb74e06355d1200db84bb8ed1ae06
Tx public key: 382c6b2b456d1b345fef3dcb5d0983d6d78b98233f407fb13041063afb11645e
Timestamp: 1712613761 Timestamp [UCT]: 2024-04-08 22:02:41 Age [y:d:h:m:s]: 01:074:22:10:53
Block: 996293 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314356 RingCT/type: yes/0
Extra: 01382c6b2b456d1b345fef3dcb5d0983d6d78b98233f407fb13041063afb11645e02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7e716b63124230914da314464c7d3b7b8421effc01172a0bbdfbbb12659bf7a 0.600000000000 1456709 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 996303, "vin": [ { "gen": { "height": 996293 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7e716b63124230914da314464c7d3b7b8421effc01172a0bbdfbbb12659bf7a" } } ], "extra": [ 1, 56, 44, 107, 43, 69, 109, 27, 52, 95, 239, 61, 203, 93, 9, 131, 214, 215, 139, 152, 35, 63, 64, 127, 177, 48, 65, 6, 58, 251, 17, 100, 94, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8