Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a498aefa67e23a771c6795d1662d63effeb36e070f72b7e0fb9fa5529208cbd

Tx prefix hash: 4d6a8fa3c308963c75f317413f8e01ae872bc1013e9dfb455f3d70b8211c6426
Tx public key: 506c08d19b85e0ec07bd5423313c0a2f87d3eed59374bfc1df39acbb66d18087
Timestamp: 1714115167 Timestamp [UCT]: 2024-04-26 07:06:07 Age [y:d:h:m:s]: 00:305:07:22:11
Block: 1008767 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218223 RingCT/type: yes/0
Extra: 01506c08d19b85e0ec07bd5423313c0a2f87d3eed59374bfc1df39acbb66d1808702110000000118ec9060000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 466144f7cab85b5e92be0d5193980adb3d4b9a6051e841d9ccaa845d3cd5d01b 0.600000000000 1470245 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": 1008777, "vin": [ { "gen": { "height": 1008767 } } ], "vout": [ { "amount": 600000000, "target": { "key": "466144f7cab85b5e92be0d5193980adb3d4b9a6051e841d9ccaa845d3cd5d01b" } } ], "extra": [ 1, 80, 108, 8, 209, 155, 133, 224, 236, 7, 189, 84, 35, 49, 60, 10, 47, 135, 211, 238, 213, 147, 116, 191, 193, 223, 57, 172, 187, 102, 209, 128, 135, 2, 17, 0, 0, 0, 1, 24, 236, 144, 96, 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