Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 967e9ed08dc98a849b65e1a1c87ee6ffdde558de1a8ce0ba728441f1eb48db3b

Tx prefix hash: 591b49855beddfd6cd88c519b4ec483c3f1295b28bf8bc54b533cdcfc9b06e07
Tx public key: 5c733792672fecc425f9786dc47d67e25cab8e9821c6cbc638861b0093fb78a6
Timestamp: 1754856264 Timestamp [UCT]: 2025-08-10 20:04:24 Age [y:d:h:m:s]: 00:109:09:46:51
Block: 1344345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77423 RingCT/type: yes/0
Extra: 015c733792672fecc425f9786dc47d67e25cab8e9821c6cbc638861b0093fb78a6021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f537470f88eaa47025cb6efb752899fc32d766fbbf4be7e86e4b1b27dcfc789 0.600000000000 1832228 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": 1344355, "vin": [ { "gen": { "height": 1344345 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f537470f88eaa47025cb6efb752899fc32d766fbbf4be7e86e4b1b27dcfc789" } } ], "extra": [ 1, 92, 115, 55, 146, 103, 47, 236, 196, 37, 249, 120, 109, 196, 125, 103, 226, 92, 171, 142, 152, 33, 198, 203, 198, 56, 134, 27, 0, 147, 251, 120, 166, 2, 17, 0, 0, 0, 2, 161, 29, 186, 152, 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