Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9c822f1f520a8614a594e0e32e736ad9a5aa932f1ae2549bac3d0409859db95

Tx prefix hash: 9f5962ce1dbacfff29d316c6913ebf4f73b33899ba89e29bf9055bb9ae268ec1
Tx public key: 6f4b2cd0a20b936b729e14a97ba029754d66e2997cc89c6031242b9b20ad184d
Timestamp: 1741148809 Timestamp [UCT]: 2025-03-05 04:26:49 Age [y:d:h:m:s]: 00:009:05:22:27
Block: 1232427 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6616 RingCT/type: yes/0
Extra: 016f4b2cd0a20b936b729e14a97ba029754d66e2997cc89c6031242b9b20ad184d02110000000d1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: acc0d7787d421e6cc13ec53e83d90e2f05e776a11c2a99734082b358afc12607 0.600000000000 1719340 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": 1232437, "vin": [ { "gen": { "height": 1232427 } } ], "vout": [ { "amount": 600000000, "target": { "key": "acc0d7787d421e6cc13ec53e83d90e2f05e776a11c2a99734082b358afc12607" } } ], "extra": [ 1, 111, 75, 44, 208, 162, 11, 147, 107, 114, 158, 20, 169, 123, 160, 41, 117, 77, 102, 226, 153, 124, 200, 156, 96, 49, 36, 43, 155, 32, 173, 24, 77, 2, 17, 0, 0, 0, 13, 31, 10, 83, 235, 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