Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d4b90eede1928a411f02240beb0979b12d38a55e9abdd1256b4aeb4ff313c7b

Tx prefix hash: 2f6b41d836a5954742550322d0f0e030666c005f3ed44b7b46536df7789b18bc
Tx public key: ccd90e8645d3d4e0caba67e8c2c32c3254a83d8e533035dd9cc834156261bfd6
Timestamp: 1726662684 Timestamp [UCT]: 2024-09-18 12:31:24 Age [y:d:h:m:s]: 00:222:00:32:19
Block: 1112790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158526 RingCT/type: yes/0
Extra: 01ccd90e8645d3d4e0caba67e8c2c32c3254a83d8e533035dd9cc834156261bfd602110000000de914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dae83842052a1487aabdfb2833b536077ce5ba6dde6a4645b722c2bc1911fd3a 0.600000000000 1592233 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": 1112800, "vin": [ { "gen": { "height": 1112790 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dae83842052a1487aabdfb2833b536077ce5ba6dde6a4645b722c2bc1911fd3a" } } ], "extra": [ 1, 204, 217, 14, 134, 69, 211, 212, 224, 202, 186, 103, 232, 194, 195, 44, 50, 84, 168, 61, 142, 83, 48, 53, 221, 156, 200, 52, 21, 98, 97, 191, 214, 2, 17, 0, 0, 0, 13, 233, 20, 221, 21, 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