Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5f2af2053a4d2351a706ea106a79b9f93dcfc896998da132ba8901a6a1fbf9e

Tx prefix hash: 3b53b23462ed90effbc80c784541c73642c1dc13aef432471038ddbe3baabeff
Tx public key: 26e9e1963b50d052a2e9e423c55136a1a06a9d2b02f4fa9d2b17e58d1372f6a2
Timestamp: 1760180863 Timestamp [UCT]: 2025-10-11 11:07:43 Age [y:d:h:m:s]: 00:110:05:27:45
Block: 1387560 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78743 RingCT/type: yes/0
Extra: 0126e9e1963b50d052a2e9e423c55136a1a06a9d2b02f4fa9d2b17e58d1372f6a2021100000001163191ee000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6b7f633617f22160f8cc8733789cc552b640e4104d2470c573f8524fc53b2f9 0.600000000000 1875755 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": 1387570, "vin": [ { "gen": { "height": 1387560 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6b7f633617f22160f8cc8733789cc552b640e4104d2470c573f8524fc53b2f9" } } ], "extra": [ 1, 38, 233, 225, 150, 59, 80, 208, 82, 162, 233, 228, 35, 197, 81, 54, 161, 160, 106, 157, 43, 2, 244, 250, 157, 43, 23, 229, 141, 19, 114, 246, 162, 2, 17, 0, 0, 0, 1, 22, 49, 145, 238, 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