Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a1e17dd0c44799888c2ff4ac12dec92114d23a5fe11ae77488f30d279649552

Tx prefix hash: 5691f2d5946bcb2ad35e7757a3cb1cf3efe8d7d1727f43e2d1e671e5b68d9f01
Tx public key: 7471d957d1a8c9c504788cec94991dfcc8e866910f577fa0202b367c7ba4cd44
Timestamp: 1710569785 Timestamp [UCT]: 2024-03-16 06:16:25 Age [y:d:h:m:s]: 01:010:05:15:34
Block: 979400 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268240 RingCT/type: yes/0
Extra: 017471d957d1a8c9c504788cec94991dfcc8e866910f577fa0202b367c7ba4cd440211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f712280539f9d07790d5d215c02d63066f1eaab329ad1106a778196d8cff95f 0.600000000000 1439433 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": 979410, "vin": [ { "gen": { "height": 979400 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f712280539f9d07790d5d215c02d63066f1eaab329ad1106a778196d8cff95f" } } ], "extra": [ 1, 116, 113, 217, 87, 209, 168, 201, 197, 4, 120, 140, 236, 148, 153, 29, 252, 200, 232, 102, 145, 15, 87, 127, 160, 32, 43, 54, 124, 123, 164, 205, 68, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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