Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c20c5b8f426c9b4cfb279c4339e5e0079047a552ec4f8f3820e44136367fa23

Tx prefix hash: 110aadab5829400a05379f035462c87cec856d1e76e94d7f8883e4190a05a9a4
Tx public key: e85097fd1abaf9ccfa3dcd0be029529f5604ed7c8b29bb0943ff1ee820ce9ccc
Timestamp: 1682433491 Timestamp [UCT]: 2023-04-25 14:38:11 Age [y:d:h:m:s]: 02:034:16:10:22
Block: 746358 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 546960 RingCT/type: yes/0
Extra: 01e85097fd1abaf9ccfa3dcd0be029529f5604ed7c8b29bb0943ff1ee820ce9ccc021100000003b3164c24000000000000000000

1 output(s) for total of 2.065410243000 dcy

stealth address amount amount idx
00: d01d68664c3a41c97da20c0acee2754b84d84d1d9e086d5a12ffcc788a42cbcd 2.065410243000 1193911 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": 746368, "vin": [ { "gen": { "height": 746358 } } ], "vout": [ { "amount": 2065410243, "target": { "key": "d01d68664c3a41c97da20c0acee2754b84d84d1d9e086d5a12ffcc788a42cbcd" } } ], "extra": [ 1, 232, 80, 151, 253, 26, 186, 249, 204, 250, 61, 205, 11, 224, 41, 82, 159, 86, 4, 237, 124, 139, 41, 187, 9, 67, 255, 30, 232, 32, 206, 156, 204, 2, 17, 0, 0, 0, 3, 179, 22, 76, 36, 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