Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a31c7b96465ae7fb7cf7455d4c2cfcf7e9fc3811f40e5ffa5681c42d474ce75c

Tx prefix hash: 2bf7cda888a9f27db57a3a6bfd582354debef23fae7e665b8a9cd164c399edca
Tx public key: e67b3b772d559bf73dbc8f9ff9de25bd8ee4329ee3b29f94db47b90824b97d36
Timestamp: 1707307276 Timestamp [UCT]: 2024-02-07 12:01:16 Age [y:d:h:m:s]: 01:057:01:29:20
Block: 952319 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301838 RingCT/type: yes/0
Extra: 01e67b3b772d559bf73dbc8f9ff9de25bd8ee4329ee3b29f94db47b90824b97d3602110000000410a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 836a0a81a38736b2866adb4d3cfff132bd67d1b87a68bc27586dcbe81dc0dce7 0.600000000000 1411241 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": 952329, "vin": [ { "gen": { "height": 952319 } } ], "vout": [ { "amount": 600000000, "target": { "key": "836a0a81a38736b2866adb4d3cfff132bd67d1b87a68bc27586dcbe81dc0dce7" } } ], "extra": [ 1, 230, 123, 59, 119, 45, 85, 155, 247, 61, 188, 143, 159, 249, 222, 37, 189, 142, 228, 50, 158, 227, 178, 159, 148, 219, 71, 185, 8, 36, 185, 125, 54, 2, 17, 0, 0, 0, 4, 16, 161, 116, 143, 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