Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4b955015eb5fb382503dc7b0a3e7453efab4f4e3bb6232594efb40c3d82320f

Tx prefix hash: d5bfc1bc6d11b7739e191868dd7717c68b36ccc42cd83a95c291e9199c0ed055
Tx public key: 009fdf05363f698359552893e5f3f042a5d47c56b7b0adefc0e141c0c460fcdd
Timestamp: 1732412023 Timestamp [UCT]: 2024-11-24 01:33:43 Age [y:d:h:m:s]: 00:121:20:35:46
Block: 1160359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86898 RingCT/type: yes/0
Extra: 01009fdf05363f698359552893e5f3f042a5d47c56b7b0adefc0e141c0c460fcdd0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 21c333574bdd141f1e719e1c4f787fb185e5fae98afc6a3792325a52d3e0c7c3 0.600000000000 1646004 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": 1160369, "vin": [ { "gen": { "height": 1160359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "21c333574bdd141f1e719e1c4f787fb185e5fae98afc6a3792325a52d3e0c7c3" } } ], "extra": [ 1, 0, 159, 223, 5, 54, 63, 105, 131, 89, 85, 40, 147, 229, 243, 240, 66, 165, 212, 124, 86, 183, 176, 173, 239, 192, 225, 65, 192, 196, 96, 252, 221, 2, 17, 0, 0, 0, 1, 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