Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33cc9dfb1282dc950b76ca9d8829d16721db0a92ed3c209aef494c427d87a7ed

Tx prefix hash: 87a092dcb438df117dc46434ab9c685cc208700fc677e261f35d50e1aae97fa3
Tx public key: cfa22ce563059a0ded385c263755e118beac227f6ce597affd8b42f0d3804dc0
Timestamp: 1645265843 Timestamp [UCT]: 2022-02-19 10:17:23 Age [y:d:h:m:s]: 03:024:08:49:29
Block: 441848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 797474 RingCT/type: yes/0
Extra: 01cfa22ce563059a0ded385c263755e118beac227f6ce597affd8b42f0d3804dc0021100000004a272b9cb000000000000000000

1 output(s) for total of 21.085040856000 dcy

stealth address amount amount idx
00: 3f83bb7974a03793bf6dc7e3dfbb2ad6bc224cd1bb1606a7d75a7b69645d9380 21.085040856000 854497 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": 441858, "vin": [ { "gen": { "height": 441848 } } ], "vout": [ { "amount": 21085040856, "target": { "key": "3f83bb7974a03793bf6dc7e3dfbb2ad6bc224cd1bb1606a7d75a7b69645d9380" } } ], "extra": [ 1, 207, 162, 44, 229, 99, 5, 154, 13, 237, 56, 92, 38, 55, 85, 225, 24, 190, 172, 34, 127, 108, 229, 151, 175, 253, 139, 66, 240, 211, 128, 77, 192, 2, 17, 0, 0, 0, 4, 162, 114, 185, 203, 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