Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 453c9078d0459a96ead36f18e1fb24eff30ede706250bb9d1b1f57db9b2dfed6

Tx prefix hash: c9312844328ec7072b086050ba3fc0968bd15466bd49f5ec752db17c22afd1aa
Tx public key: 2e4017ac09241fefdf3469e2d10a0d88f8fe4d5be87b3872e5c09ce68d3a0c00
Timestamp: 1720540387 Timestamp [UCT]: 2024-07-09 15:53:07 Age [y:d:h:m:s]: 00:311:07:39:26
Block: 1062039 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222454 RingCT/type: yes/0
Extra: 012e4017ac09241fefdf3469e2d10a0d88f8fe4d5be87b3872e5c09ce68d3a0c0002110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 863975ffea496696223b1c771e79af94faeff19dddcd374c75eb21b691f072f1 0.600000000000 1532540 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": 1062049, "vin": [ { "gen": { "height": 1062039 } } ], "vout": [ { "amount": 600000000, "target": { "key": "863975ffea496696223b1c771e79af94faeff19dddcd374c75eb21b691f072f1" } } ], "extra": [ 1, 46, 64, 23, 172, 9, 36, 31, 239, 223, 52, 105, 226, 209, 10, 13, 136, 248, 254, 77, 91, 232, 123, 56, 114, 229, 192, 156, 230, 141, 58, 12, 0, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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