Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 326e19f7da0448cecf2e82f29b5350a48e1a5ce2e162ce39e5595d64f941bed2

Tx prefix hash: adbaef236cc94adf77f69db30f120ed3e587515ba6460c1c4cf8776594b74f46
Tx public key: 010a76f9488b2551c492b13f0f8e571d44e0c8d3950076aac7a5e7d8963b40e7
Timestamp: 1760539183 Timestamp [UCT]: 2025-10-15 14:39:43 Age [y:d:h:m:s]: 00:076:04:48:58
Block: 1390530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54557 RingCT/type: yes/0
Extra: 01010a76f9488b2551c492b13f0f8e571d44e0c8d3950076aac7a5e7d8963b40e70211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7501a89c52c6d508725c2a90169cdac28074a6701a73e748e3051a9e327b9d7c 0.600000000000 1878775 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": 1390540, "vin": [ { "gen": { "height": 1390530 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7501a89c52c6d508725c2a90169cdac28074a6701a73e748e3051a9e327b9d7c" } } ], "extra": [ 1, 1, 10, 118, 249, 72, 139, 37, 81, 196, 146, 177, 63, 15, 142, 87, 29, 68, 224, 200, 211, 149, 0, 118, 170, 199, 165, 231, 216, 150, 59, 64, 231, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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