Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ad6dc6906ad6d055d79e3731a9bb2d70a308f0a1ffbb00d606462e72ccce2d0a

Tx prefix hash: d220fe3e672afda57f64fa95e329ffd86efc013d3238fe93c7059e50e2c904a4
Tx public key: 0cee0ca4934e87500a06b53d86c746c15b7a3341b0f9e13248d1d4ecdb4125b5
Timestamp: 1765145134 Timestamp [UCT]: 2025-12-07 22:05:34 Age [y:d:h:m:s]: 00:016:01:27:36
Block: 1428701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 11482 RingCT/type: yes/0
Extra: 010cee0ca4934e87500a06b53d86c746c15b7a3341b0f9e13248d1d4ecdb4125b50209000000183ef0b5c200

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2dadfdbcbe986eb26bd84c3ee320e7f631e34e47d00be7550e7a3186de76d5ef 0.600000000000 1917424 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": 1428711, "vin": [ { "gen": { "height": 1428701 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2dadfdbcbe986eb26bd84c3ee320e7f631e34e47d00be7550e7a3186de76d5ef" } } ], "extra": [ 1, 12, 238, 12, 164, 147, 78, 135, 80, 10, 6, 181, 61, 134, 199, 70, 193, 91, 122, 51, 65, 176, 249, 225, 50, 72, 209, 212, 236, 219, 65, 37, 181, 2, 9, 0, 0, 0, 24, 62, 240, 181, 194, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8