Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8fd5fdc889c36bbd6ae38649b1dfef7f0248c31a90491ae969c3e330f711ff02

Tx prefix hash: d955db8f3800748e62fb182606dc02e4fc473e983a9b2e9ee0f6ad33678a514f
Tx public key: 6c0b3fc8cbe6eb29020ed60146ba35f3294f8a1b7e1eff839325ecb5259398ff
Timestamp: 1763247691 Timestamp [UCT]: 2025-11-15 23:01:31 Age [y:d:h:m:s]: 00:075:21:49:23
Block: 1412974 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54171 RingCT/type: yes/0
Extra: 016c0b3fc8cbe6eb29020ed60146ba35f3294f8a1b7e1eff839325ecb5259398ff0211000000028ceb7f09000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1e21fca89cd82e8cb78cc5bb503d3045f531b716ee53ec0d80673b228a6df13 0.600000000000 1901451 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": 1412984, "vin": [ { "gen": { "height": 1412974 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1e21fca89cd82e8cb78cc5bb503d3045f531b716ee53ec0d80673b228a6df13" } } ], "extra": [ 1, 108, 11, 63, 200, 203, 230, 235, 41, 2, 14, 214, 1, 70, 186, 53, 243, 41, 79, 138, 27, 126, 30, 255, 131, 147, 37, 236, 181, 37, 147, 152, 255, 2, 17, 0, 0, 0, 2, 140, 235, 127, 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