Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c72e50f5e7ec81448845b43d817ffe904a1c93295afad3a1a8d3446b027c231

Tx prefix hash: 79e0490c87ba2c8079d2911b38217e986e5bb7d914d8b63d7eac1816a472bdf7
Tx public key: a5b0b96ac5dba716a7862d9d35ac437eebbcbda4fca5e24558eebf74bd2430f8
Timestamp: 1703079163 Timestamp [UCT]: 2023-12-20 13:32:43 Age [y:d:h:m:s]: 01:111:13:45:50
Block: 917273 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 340873 RingCT/type: yes/0
Extra: 01a5b0b96ac5dba716a7862d9d35ac437eebbcbda4fca5e24558eebf74bd2430f8021100000001e4bb6b83000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1659378603fbb6158c26a74ab3f061b948a18b9fa60b35152b55115f49fa95df 0.600000000000 1374843 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": 917283, "vin": [ { "gen": { "height": 917273 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1659378603fbb6158c26a74ab3f061b948a18b9fa60b35152b55115f49fa95df" } } ], "extra": [ 1, 165, 176, 185, 106, 197, 219, 167, 22, 167, 134, 45, 157, 53, 172, 67, 126, 235, 188, 189, 164, 252, 165, 226, 69, 88, 238, 191, 116, 189, 36, 48, 248, 2, 17, 0, 0, 0, 1, 228, 187, 107, 131, 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