Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4da0646a9212b4a6b9b6ac27b72b7d96febd7984f49daa1f7b304f7be1a78b4b

Tx prefix hash: 26c05344c622d809c19dd64110999a853e1c9e97af6d0597aa8b175a014130f7
Tx public key: 3201563553dc229904f589e9b053ce307dd1efd010cef1a8dbeed8c12b72cbf4
Timestamp: 1723106633 Timestamp [UCT]: 2024-08-08 08:43:53 Age [y:d:h:m:s]: 00:239:07:49:26
Block: 1083310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170937 RingCT/type: yes/0
Extra: 013201563553dc229904f589e9b053ce307dd1efd010cef1a8dbeed8c12b72cbf4021100000001341001ae000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b29b06984aa3a63c514490080321e8acc4126409975a06eb4e1da28994a569d5 0.600000000000 1557173 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": 1083320, "vin": [ { "gen": { "height": 1083310 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b29b06984aa3a63c514490080321e8acc4126409975a06eb4e1da28994a569d5" } } ], "extra": [ 1, 50, 1, 86, 53, 83, 220, 34, 153, 4, 245, 137, 233, 176, 83, 206, 48, 125, 209, 239, 208, 16, 206, 241, 168, 219, 238, 216, 193, 43, 114, 203, 244, 2, 17, 0, 0, 0, 1, 52, 16, 1, 174, 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