Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71f62be73b4f4061cef0e8f2efd4655790b0606baa8050c49c7e0246f43c0217

Tx prefix hash: e76505aab5d753166f34d3725f6faf5290d0be028dde390e767094d8a3f1770d
Tx public key: 2bdefdb86e0e9f666517e0b8efa437de0b67c759185cb5f4f83be6bad7776fee
Timestamp: 1736972774 Timestamp [UCT]: 2025-01-15 20:26:14 Age [y:d:h:m:s]: 00:153:22:08:42
Block: 1198115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109712 RingCT/type: yes/0
Extra: 012bdefdb86e0e9f666517e0b8efa437de0b67c759185cb5f4f83be6bad7776fee0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6e9ab4db21f33033e98bb6a9088070d1cf06d300e12f222d64edb7e3e2a55bff 0.600000000000 1684734 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": 1198125, "vin": [ { "gen": { "height": 1198115 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6e9ab4db21f33033e98bb6a9088070d1cf06d300e12f222d64edb7e3e2a55bff" } } ], "extra": [ 1, 43, 222, 253, 184, 110, 14, 159, 102, 101, 23, 224, 184, 239, 164, 55, 222, 11, 103, 199, 89, 24, 92, 181, 244, 248, 59, 230, 186, 215, 119, 111, 238, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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