Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b2d37a888b8fc500fc85fc36545f5ffba88a3e91aba8313d67883bb438ea14a

Tx prefix hash: 5e51cacd108e4ced36e73ff011d5640c2a367e85af34f02f437fd5b72b691368
Tx public key: c3e8dc291d515ec7323f4fba83ce5ba7c8dcee64df7ad7c33df7c9c3dbd6d676
Timestamp: 1745308623 Timestamp [UCT]: 2025-04-22 07:57:03 Age [y:d:h:m:s]: 00:212:23:48:36
Block: 1266863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149937 RingCT/type: yes/0
Extra: 01c3e8dc291d515ec7323f4fba83ce5ba7c8dcee64df7ad7c33df7c9c3dbd6d676021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e394a08b695726c21468270df848526cf3bf8cfe738ed1394617d7181387981b 0.600000000000 1754086 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": 1266873, "vin": [ { "gen": { "height": 1266863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e394a08b695726c21468270df848526cf3bf8cfe738ed1394617d7181387981b" } } ], "extra": [ 1, 195, 232, 220, 41, 29, 81, 94, 199, 50, 63, 79, 186, 131, 206, 91, 167, 200, 220, 238, 100, 223, 122, 215, 195, 61, 247, 201, 195, 219, 214, 214, 118, 2, 17, 0, 0, 0, 1, 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