Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3ce70997a04b4b5dfb699405a489c1d6f10e1526c27fc193ce94618de98fb4f

Tx prefix hash: 704b3f891e85abe79041e26d4e2f0e731363e03ed947c277bcec373737289060
Tx public key: 00370f118f8c812d2334edacffc9f8a2920dc82f1005108b6c145504e565eacf
Timestamp: 1709259669 Timestamp [UCT]: 2024-03-01 02:21:09 Age [y:d:h:m:s]: 01:090:01:12:24
Block: 968522 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325405 RingCT/type: yes/0
Extra: 0100370f118f8c812d2334edacffc9f8a2920dc82f1005108b6c145504e565eacf0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ebfb2e3cd2e7840ad3217325ae0870d081be089eec6ec71c78ce0df200efda50 0.600000000000 1428337 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": 968532, "vin": [ { "gen": { "height": 968522 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ebfb2e3cd2e7840ad3217325ae0870d081be089eec6ec71c78ce0df200efda50" } } ], "extra": [ 1, 0, 55, 15, 17, 143, 140, 129, 45, 35, 52, 237, 172, 255, 201, 248, 162, 146, 13, 200, 47, 16, 5, 16, 139, 108, 20, 85, 4, 229, 101, 234, 207, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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