Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76021c73098186b79d31de145a8253585f82cabef9b5827ad975922b4c9378dc

Tx prefix hash: 8c080db19c080ca99b47279e64492c1571920d7a46a5b2b2eecaac45abb82f4f
Tx public key: f63e4d251f705ead3c4e5f563aab714ea412b37b70dcf2dcc9e21721ac8f6db1
Timestamp: 1765198384 Timestamp [UCT]: 2025-12-08 12:53:04 Age [y:d:h:m:s]: 00:030:03:11:16
Block: 1429140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 21584 RingCT/type: yes/0
Extra: 01f63e4d251f705ead3c4e5f563aab714ea412b37b70dcf2dcc9e21721ac8f6db102090000000fd48050ef00

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d6e5d9a04cc19c54967909c8b798275438e3790845e015ae42200e932cacaff 0.600000000000 1917863 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": 1429150, "vin": [ { "gen": { "height": 1429140 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d6e5d9a04cc19c54967909c8b798275438e3790845e015ae42200e932cacaff" } } ], "extra": [ 1, 246, 62, 77, 37, 31, 112, 94, 173, 60, 78, 95, 86, 58, 171, 113, 78, 164, 18, 179, 123, 112, 220, 242, 220, 201, 226, 23, 33, 172, 143, 109, 177, 2, 9, 0, 0, 0, 15, 212, 128, 80, 239, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8