Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7625b01b21549fcd2ee9d89492d95e00c41d4712e3e04f3d0466f88581f926b9

Tx prefix hash: f690afd2fb5deb34d24653674efb9da1db42228853e9cd322fe405fabaa6be07
Tx public key: 61daa50da2b69263d95e3bce45680fb69999e868c78aaf413f4673f946cddde7
Timestamp: 1632119764 Timestamp [UCT]: 2021-09-20 06:36:04 Age [y:d:h:m:s]: 03:047:16:46:10
Block: 337378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 810016 RingCT/type: yes/0
Extra: 0161daa50da2b69263d95e3bce45680fb69999e868c78aaf413f4673f946cddde702110000001bfdc024ec000000000000000000

1 output(s) for total of 46.787201539000 dcy

stealth address amount amount idx
00: 775f0e1071c8b3a9e92e112fcf2e15339622879c04694bdfab1dcdcb1b2620d3 46.787201539000 694727 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": 337388, "vin": [ { "gen": { "height": 337378 } } ], "vout": [ { "amount": 46787201539, "target": { "key": "775f0e1071c8b3a9e92e112fcf2e15339622879c04694bdfab1dcdcb1b2620d3" } } ], "extra": [ 1, 97, 218, 165, 13, 162, 182, 146, 99, 217, 94, 59, 206, 69, 104, 15, 182, 153, 153, 232, 104, 199, 138, 175, 65, 63, 70, 115, 249, 70, 205, 221, 231, 2, 17, 0, 0, 0, 27, 253, 192, 36, 236, 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