Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 618f5acc0eccc101b8b2c47da8a125dbf1a11ee30d9d5fc80684554a5b1f6465

Tx prefix hash: 26a4147b0b31f1f3ae9bce51c877db54504dea795f752f1e5a743a2b2cf5f23c
Tx public key: ac5201f9fbee4a0dacb7357dc04103ee6474e8887621d8de06030bc0b47ebff6
Timestamp: 1713874106 Timestamp [UCT]: 2024-04-23 12:08:26 Age [y:d:h:m:s]: 00:253:01:55:46
Block: 1006767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 181157 RingCT/type: yes/0
Extra: 01ac5201f9fbee4a0dacb7357dc04103ee6474e8887621d8de06030bc0b47ebff60211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 016064e4a84085f7e1f1f0b26a4bac8f4147f35cbf1894451a134504faa43c81 0.600000000000 1467899 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": 1006777, "vin": [ { "gen": { "height": 1006767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "016064e4a84085f7e1f1f0b26a4bac8f4147f35cbf1894451a134504faa43c81" } } ], "extra": [ 1, 172, 82, 1, 249, 251, 238, 74, 13, 172, 183, 53, 125, 192, 65, 3, 238, 100, 116, 232, 136, 118, 33, 216, 222, 6, 3, 11, 192, 180, 126, 191, 246, 2, 17, 0, 0, 0, 7, 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