Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4546f2bdcd6632334f4bd33b737ddda824fcec2396baad9b3ef5181cf7d960f9

Tx prefix hash: 11e90a3aa21574a589fb896654b9e28b38f9b88ce4554c9fd71bfbb0dffc0a21
Tx public key: 4a6d10d06c776c8245aa5411d9de8984fc1628af12b689ea79d42b13acd3ec3e
Timestamp: 1711324679 Timestamp [UCT]: 2024-03-24 23:57:59 Age [y:d:h:m:s]: 01:070:00:02:22
Block: 985654 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311023 RingCT/type: yes/0
Extra: 014a6d10d06c776c8245aa5411d9de8984fc1628af12b689ea79d42b13acd3ec3e0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fffa29b41b16f3666787ad5d9cfd2a14a6ff23a56253f9cb1857ab1285a9aff4 0.600000000000 1445871 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": 985664, "vin": [ { "gen": { "height": 985654 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fffa29b41b16f3666787ad5d9cfd2a14a6ff23a56253f9cb1857ab1285a9aff4" } } ], "extra": [ 1, 74, 109, 16, 208, 108, 119, 108, 130, 69, 170, 84, 17, 217, 222, 137, 132, 252, 22, 40, 175, 18, 182, 137, 234, 121, 212, 43, 19, 172, 211, 236, 62, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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