Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e22ead4f97d21a72dc1c95fc5f7482f52c6dff5819b6b744687c53f563a4c9bf

Tx prefix hash: a50a7dd4719f745113a914e1424c6f54813c72dbe5b10b9388e2ed1858adb7e1
Tx public key: c10b0d1fe9ab96ab321e23a2900b609e3c8e3a70bd22f90bbb7c0a4d71dc9200
Timestamp: 1728159205 Timestamp [UCT]: 2024-10-05 20:13:25 Age [y:d:h:m:s]: 00:178:22:53:44
Block: 1125205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127684 RingCT/type: yes/0
Extra: 01c10b0d1fe9ab96ab321e23a2900b609e3c8e3a70bd22f90bbb7c0a4d71dc920002110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d269b83e902a6e5cf342e6de21a1194273a3a97a41df03c1688d2a9ced1cba24 0.600000000000 1607882 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": 1125215, "vin": [ { "gen": { "height": 1125205 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d269b83e902a6e5cf342e6de21a1194273a3a97a41df03c1688d2a9ced1cba24" } } ], "extra": [ 1, 193, 11, 13, 31, 233, 171, 150, 171, 50, 30, 35, 162, 144, 11, 96, 158, 60, 142, 58, 112, 189, 34, 249, 11, 187, 124, 10, 77, 113, 220, 146, 0, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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