Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 476d74f5bbefd5161fad7f67a4b5a62cb6f4c24e6f795ac782f42d3a4c49d0fa

Tx prefix hash: 9648f1926461135cce2a5569901b6813384a5c700cf80dba1360ac727971d553
Tx public key: cef676fa0cff6fa7a29613e728767ec57d9def8f0fe7ad1b0b52391df4d94a36
Timestamp: 1762060026 Timestamp [UCT]: 2025-11-02 05:07:06 Age [y:d:h:m:s]: 00:004:17:09:33
Block: 1403139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3366 RingCT/type: yes/0
Extra: 01cef676fa0cff6fa7a29613e728767ec57d9def8f0fe7ad1b0b52391df4d94a36021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64a73df6b0d50c417a204d2c4046302940f058c7009a0f5a165db86e82965f01 0.600000000000 1891466 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": 1403149, "vin": [ { "gen": { "height": 1403139 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64a73df6b0d50c417a204d2c4046302940f058c7009a0f5a165db86e82965f01" } } ], "extra": [ 1, 206, 246, 118, 250, 12, 255, 111, 167, 162, 150, 19, 231, 40, 118, 126, 197, 125, 157, 239, 143, 15, 231, 173, 27, 11, 82, 57, 29, 244, 217, 74, 54, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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