Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 510e234b523cdd7ca85be20ea317ff64a9978ba7bac7ea0ed9171110fce71f8d

Tx prefix hash: 97bbda4daabfbba6327823407206e2988dd0a698d6bd550fde8f3cc8f851d047
Tx public key: 2bc2dbdcec22092f9c86cc5c51c22d96a0374050bf874f5fcae6476836e8fa9f
Timestamp: 1714204033 Timestamp [UCT]: 2024-04-27 07:47:13 Age [y:d:h:m:s]: 00:355:21:13:56
Block: 1009498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254419 RingCT/type: yes/0
Extra: 012bc2dbdcec22092f9c86cc5c51c22d96a0374050bf874f5fcae6476836e8fa9f0211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 990ac82c57b52e78cb06edb91603510ccf2c0f6abdd7aacc46c1f2f28a0e4dd2 0.600000000000 1471184 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": 1009508, "vin": [ { "gen": { "height": 1009498 } } ], "vout": [ { "amount": 600000000, "target": { "key": "990ac82c57b52e78cb06edb91603510ccf2c0f6abdd7aacc46c1f2f28a0e4dd2" } } ], "extra": [ 1, 43, 194, 219, 220, 236, 34, 9, 47, 156, 134, 204, 92, 81, 194, 45, 150, 160, 55, 64, 80, 191, 135, 79, 95, 202, 230, 71, 104, 54, 232, 250, 159, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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