Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa0a6e1c027818fb175320426d3bd92d0fe002b54816ac12d8b1aa693af40aa7

Tx prefix hash: 922484e07ebfb99d62f1c20e8ff7fdee88e67afc5d3d31c5420d5fce78bb4923
Tx public key: d47d6f9180b3b9cfe970937efcf77e4bb767d1d1e71ed250098375ae25d4da6a
Timestamp: 1711318305 Timestamp [UCT]: 2024-03-24 22:11:45 Age [y:d:h:m:s]: 01:016:07:03:50
Block: 985601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272602 RingCT/type: yes/0
Extra: 01d47d6f9180b3b9cfe970937efcf77e4bb767d1d1e71ed250098375ae25d4da6a02110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16780ac991486ff6934bd87bd653489f33583b6cffc7de23349548cbb697eef9 0.600000000000 1445818 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": 985611, "vin": [ { "gen": { "height": 985601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16780ac991486ff6934bd87bd653489f33583b6cffc7de23349548cbb697eef9" } } ], "extra": [ 1, 212, 125, 111, 145, 128, 179, 185, 207, 233, 112, 147, 126, 252, 247, 126, 75, 183, 103, 209, 209, 231, 30, 210, 80, 9, 131, 117, 174, 37, 212, 218, 106, 2, 17, 0, 0, 0, 10, 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