Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5ebfaf872d04c56cc160552d968381737e9feb71f32886fe0e69bed9b19809c

Tx prefix hash: 056dae732c00bd9aba72ebc4be2efa17cb6b50f21f6fecad0f065547701fcb62
Tx public key: 5510dd12d62af9d87471f8d3ba4f67b7d18be760b541c0b5d5d7ec2c2c1212c6
Timestamp: 1751125164 Timestamp [UCT]: 2025-06-28 15:39:24 Age [y:d:h:m:s]: 00:193:12:11:22
Block: 1314617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136451 RingCT/type: yes/0
Extra: 015510dd12d62af9d87471f8d3ba4f67b7d18be760b541c0b5d5d7ec2c2c1212c6021100000003a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0af20196733e5fd14c288e9e9848475646145751a4b47ff3f2236cf1f632b246 0.600000000000 1802266 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": 1314627, "vin": [ { "gen": { "height": 1314617 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0af20196733e5fd14c288e9e9848475646145751a4b47ff3f2236cf1f632b246" } } ], "extra": [ 1, 85, 16, 221, 18, 214, 42, 249, 216, 116, 113, 248, 211, 186, 79, 103, 183, 209, 139, 231, 96, 181, 65, 192, 181, 213, 215, 236, 44, 44, 18, 18, 198, 2, 17, 0, 0, 0, 3, 161, 29, 186, 152, 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