Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69ebcc42c12378bedb5c53b29f7cde4a48eae9054d1d8bc895e81639503c67c6

Tx prefix hash: 976cf159e45b98029c51bbead72f25e204e496c378306413dd62fbd1bf916d56
Tx public key: 6ba5a240e46f620ce84c8308d7f1faa7286359d2912f21ac8bc8b6ba2f07d90a
Timestamp: 1699505294 Timestamp [UCT]: 2023-11-09 04:48:14 Age [y:d:h:m:s]: 01:360:23:06:49
Block: 887641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 516889 RingCT/type: yes/0
Extra: 016ba5a240e46f620ce84c8308d7f1faa7286359d2912f21ac8bc8b6ba2f07d90a0211000000024b8f5122000000000000000000

1 output(s) for total of 0.702873049000 dcy

stealth address amount amount idx
00: 26a8b1babd4738752be341bfe60f6db6c0ee6f612d72f61d92e8efd8e85d3337 0.702873049000 1343534 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": 887651, "vin": [ { "gen": { "height": 887641 } } ], "vout": [ { "amount": 702873049, "target": { "key": "26a8b1babd4738752be341bfe60f6db6c0ee6f612d72f61d92e8efd8e85d3337" } } ], "extra": [ 1, 107, 165, 162, 64, 228, 111, 98, 12, 232, 76, 131, 8, 215, 241, 250, 167, 40, 99, 89, 210, 145, 47, 33, 172, 139, 200, 182, 186, 47, 7, 217, 10, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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