Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02d610dfd32dc6bb91bbe472d2eefba40f4738521d98c2c84aa6f39ef0ac563d

Tx prefix hash: 9fbaf4f53581645be82ff4f16329bc89e98e26b8404839882f5a6d7ae39054a9
Tx public key: 1dd236c0bd652176f1542cf71738b5dc577c9e7a96155a2fe9d919f258b2e621
Timestamp: 1751213281 Timestamp [UCT]: 2025-06-29 16:08:01 Age [y:d:h:m:s]: 00:143:19:55:45
Block: 1315275 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100944 RingCT/type: yes/0
Extra: 011dd236c0bd652176f1542cf71738b5dc577c9e7a96155a2fe9d919f258b2e621021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5bd7557cd264d7adfd62960cb06ed60f6d25f8817cc6b45c97aa308cce5ffbea 0.600000000000 1802928 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": 1315285, "vin": [ { "gen": { "height": 1315275 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5bd7557cd264d7adfd62960cb06ed60f6d25f8817cc6b45c97aa308cce5ffbea" } } ], "extra": [ 1, 29, 210, 54, 192, 189, 101, 33, 118, 241, 84, 44, 247, 23, 56, 181, 220, 87, 124, 158, 122, 150, 21, 90, 47, 233, 217, 25, 242, 88, 178, 230, 33, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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