Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9ca982e008af63123a102ae0832d909b6714ae83b6840d716241bf41849c1d7

Tx prefix hash: c921ab65cc39fa2bc42ae4bfe177a0d1249e9974fc5bf1efb9fe3581d9cdad7c
Tx public key: 2f1af20c6b0a4a9ee5c4f2566bd6fb6388d90f0d921c6a8483b3f671fb7b607a
Timestamp: 1708758168 Timestamp [UCT]: 2024-02-24 07:02:48 Age [y:d:h:m:s]: 01:033:22:03:13
Block: 964356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285254 RingCT/type: yes/0
Extra: 012f1af20c6b0a4a9ee5c4f2566bd6fb6388d90f0d921c6a8483b3f671fb7b607a02110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 248b9781c8b13342204500e79459513a76fee136de29ab3415849d856b39958a 0.600000000000 1424087 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": 964366, "vin": [ { "gen": { "height": 964356 } } ], "vout": [ { "amount": 600000000, "target": { "key": "248b9781c8b13342204500e79459513a76fee136de29ab3415849d856b39958a" } } ], "extra": [ 1, 47, 26, 242, 12, 107, 10, 74, 158, 229, 196, 242, 86, 107, 214, 251, 99, 136, 217, 15, 13, 146, 28, 106, 132, 131, 179, 246, 113, 251, 123, 96, 122, 2, 17, 0, 0, 0, 11, 89, 218, 211, 245, 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