Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89d1e69f0eaa436ee41c3eab100565bb87da5f0324e4e35d77994873a5e08600

Tx prefix hash: 88bb9d496365fedaa0ae6f4a3c084cce123094aee517e956a6a504a04428cc04
Tx public key: 094aa222fdfbfec2c85aa9dd9e69c86130b85ddfce4034e0b3e43bc3ce5b7b93
Timestamp: 1762506356 Timestamp [UCT]: 2025-11-07 09:05:56 Age [y:d:h:m:s]: 00:050:02:18:23
Block: 1406829 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35868 RingCT/type: yes/0
Extra: 01094aa222fdfbfec2c85aa9dd9e69c86130b85ddfce4034e0b3e43bc3ce5b7b93021100000008e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02aec7344e3983aa9814d28c6148804d336b79f063568856135b50d47ec3bf84 0.600000000000 1895218 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": 1406839, "vin": [ { "gen": { "height": 1406829 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02aec7344e3983aa9814d28c6148804d336b79f063568856135b50d47ec3bf84" } } ], "extra": [ 1, 9, 74, 162, 34, 253, 251, 254, 194, 200, 90, 169, 221, 158, 105, 200, 97, 48, 184, 93, 223, 206, 64, 52, 224, 179, 228, 59, 195, 206, 91, 123, 147, 2, 17, 0, 0, 0, 8, 228, 220, 144, 9, 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