Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 593b14d73aebda4521c35719a1a06efad6885a0a26db4cd770d256f002de9641

Tx prefix hash: fd48762da5fc6164ee231fa4282a17ac6d931bff2feb38a083aac06b79754373
Tx public key: 842f1c54b51ac4f866b4ee805a08bdd718d9986dc37cbc9a133c3ba5a396e41b
Timestamp: 1763378572 Timestamp [UCT]: 2025-11-17 11:22:52 Age [y:d:h:m:s]: 00:036:04:59:03
Block: 1414061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25909 RingCT/type: yes/0
Extra: 01842f1c54b51ac4f866b4ee805a08bdd718d9986dc37cbc9a133c3ba5a396e41b021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49a3fdf3a10d6b52ecd2504f9096c115f795e06111cf565bf1ec5f28c8c59402 0.600000000000 1902546 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": 1414071, "vin": [ { "gen": { "height": 1414061 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49a3fdf3a10d6b52ecd2504f9096c115f795e06111cf565bf1ec5f28c8c59402" } } ], "extra": [ 1, 132, 47, 28, 84, 181, 26, 196, 248, 102, 180, 238, 128, 90, 8, 189, 215, 24, 217, 152, 109, 195, 124, 188, 154, 19, 60, 59, 165, 163, 150, 228, 27, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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