Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 202ac661e87625084e75a1d28709db1aae7c254f3e81cd2056cdeb7f57568bad

Tx prefix hash: a13af9e2fa1833d953e24fe29305839b05f08293485ba9a99e293fb2ab90c44d
Tx public key: d68a3bfd8d273d92aab3eee591b3097ca7f9062e8f728b64472e6b82d48c8c19
Timestamp: 1762736095 Timestamp [UCT]: 2025-11-10 00:54:55 Age [y:d:h:m:s]: 00:043:19:50:17
Block: 1408734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 31374 RingCT/type: yes/0
Extra: 01d68a3bfd8d273d92aab3eee591b3097ca7f9062e8f728b64472e6b82d48c8c19021100000002df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 466cce81232c9a44140e7904cbccee50a17fde82b42be7bf12466185789e758d 0.600000000000 1897165 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": 1408744, "vin": [ { "gen": { "height": 1408734 } } ], "vout": [ { "amount": 600000000, "target": { "key": "466cce81232c9a44140e7904cbccee50a17fde82b42be7bf12466185789e758d" } } ], "extra": [ 1, 214, 138, 59, 253, 141, 39, 61, 146, 170, 179, 238, 229, 145, 179, 9, 124, 167, 249, 6, 46, 143, 114, 139, 100, 71, 46, 107, 130, 212, 140, 140, 25, 2, 17, 0, 0, 0, 2, 223, 90, 36, 122, 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