Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5dddea505aee60522ebe1ccf7213ed3ab0bbdf62444a4ec8fa02d34ca1c16a7

Tx prefix hash: fb765497284e358c9cb981d9a9e6139fdb43dbf5befea7e6bd886f6197b229cf
Tx public key: adfbb67e99ef05157539a749989edd31ab48bfd23fd1b392f05853f6cc6f5d0c
Timestamp: 1580784440 Timestamp [UCT]: 2020-02-04 02:47:20 Age [y:d:h:m:s]: 04:337:23:09:46
Block: 58035 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1133106 RingCT/type: yes/0
Extra: 01adfbb67e99ef05157539a749989edd31ab48bfd23fd1b392f05853f6cc6f5d0c0211000000022264afe6000000000000000000

1 output(s) for total of 394.191063812000 dcy

stealth address amount amount idx
00: 267dcbb5a1c0845f8a0e1bd30246b45ee506be0b524cdadd4ac962cdadd3206c 394.191063812000 107322 of 0

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": 58045, "vin": [ { "gen": { "height": 58035 } } ], "vout": [ { "amount": 394191063812, "target": { "key": "267dcbb5a1c0845f8a0e1bd30246b45ee506be0b524cdadd4ac962cdadd3206c" } } ], "extra": [ 1, 173, 251, 182, 126, 153, 239, 5, 21, 117, 57, 167, 73, 152, 158, 221, 49, 171, 72, 191, 210, 63, 209, 179, 146, 240, 88, 83, 246, 204, 111, 93, 12, 2, 17, 0, 0, 0, 2, 34, 100, 175, 230, 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