Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a8760383320ba4feff6016b65adca091869778817c0efda9e8ec079b62633354

Tx prefix hash: da18ee25fdc99d832430e0f4da2b89f50e8a1ce81ca9fcf653363df042a6e827
Tx public key: 0d4a93495c1f51c920f268437364a6b2e7d6a51dfe7bdc13a1c3b2285be67fc3
Timestamp: 1761184258 Timestamp [UCT]: 2025-10-23 01:50:58 Age [y:d:h:m:s]: 00:016:09:31:26
Block: 1395889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11719 RingCT/type: yes/0
Extra: 010d4a93495c1f51c920f268437364a6b2e7d6a51dfe7bdc13a1c3b2285be67fc302110000000601491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 206a40de99e6c5a86c648338c49daf8959f24c0a988193b76a3964933119f58b 0.600000000000 1884172 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": 1395899, "vin": [ { "gen": { "height": 1395889 } } ], "vout": [ { "amount": 600000000, "target": { "key": "206a40de99e6c5a86c648338c49daf8959f24c0a988193b76a3964933119f58b" } } ], "extra": [ 1, 13, 74, 147, 73, 92, 31, 81, 201, 32, 242, 104, 67, 115, 100, 166, 178, 231, 214, 165, 29, 254, 123, 220, 19, 161, 195, 178, 40, 91, 230, 127, 195, 2, 17, 0, 0, 0, 6, 1, 73, 31, 136, 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