Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a057cf222fa1c8ea8f8d8f1e44f1352d96783a285cb629bce0e3391b0e2e8b2e

Tx prefix hash: 39dbe1b2f052d9ed29d29fe1309091608625ceddf79f103aef2e2f2cc26e86c2
Tx public key: 5285818ab935119adeea1c3ec767e242aaf60cc87f5f2e356feff5031cf93b52
Timestamp: 1751945190 Timestamp [UCT]: 2025-07-08 03:26:30 Age [y:d:h:m:s]: 00:198:16:36:03
Block: 1321034 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140395 RingCT/type: yes/0
Extra: 015285818ab935119adeea1c3ec767e242aaf60cc87f5f2e356feff5031cf93b52021100000004dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ea5d22262e330a4a7ca4133a0dfb8db166bc8a32fbc2a615f466d2824eefc0d 0.600000000000 1808737 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": 1321044, "vin": [ { "gen": { "height": 1321034 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ea5d22262e330a4a7ca4133a0dfb8db166bc8a32fbc2a615f466d2824eefc0d" } } ], "extra": [ 1, 82, 133, 129, 138, 185, 53, 17, 154, 222, 234, 28, 62, 199, 103, 226, 66, 170, 246, 12, 200, 127, 95, 46, 53, 111, 239, 245, 3, 28, 249, 59, 82, 2, 17, 0, 0, 0, 4, 223, 195, 186, 73, 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