Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ac223fde7b53f0df97045d2106104c12b19d2c916388560f1bddc49a1c40d55

Tx prefix hash: e9842a9662c2e0414a458b4bd3525176978dfc93331c50e69b1510e1d31b3f3e
Tx public key: 4782a86981b6c1787dd9e67d0b0518d989f07695673eb5a9f28e90a9c3897b74
Timestamp: 1762007362 Timestamp [UCT]: 2025-11-01 14:29:22 Age [y:d:h:m:s]: 00:005:04:22:10
Block: 1402722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3675 RingCT/type: yes/0
Extra: 014782a86981b6c1787dd9e67d0b0518d989f07695673eb5a9f28e90a9c3897b74021100000004df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78321696181a3452be6b847ec708146e0a3a9d2c667a681e65c719adf4a05491 0.600000000000 1891041 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": 1402732, "vin": [ { "gen": { "height": 1402722 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78321696181a3452be6b847ec708146e0a3a9d2c667a681e65c719adf4a05491" } } ], "extra": [ 1, 71, 130, 168, 105, 129, 182, 193, 120, 125, 217, 230, 125, 11, 5, 24, 217, 137, 240, 118, 149, 103, 62, 181, 169, 242, 142, 144, 169, 195, 137, 123, 116, 2, 17, 0, 0, 0, 4, 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