Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0545de51946e8d13b1b1672c62ac77a177a4e2e17e7cfc1ad331cd6efd3f87e

Tx prefix hash: e556d68be0072052c3b9f1201b9184c7203d090fcee52c3fa93dace9c8a0721a
Tx public key: e6e15dffd439de0c2de68b90d17f0a80f4505c02ff4a01392ca48d3753a40deb
Timestamp: 1760670445 Timestamp [UCT]: 2025-10-17 03:07:25 Age [y:d:h:m:s]: 00:076:14:06:43
Block: 1391621 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54831 RingCT/type: yes/0
Extra: 01e6e15dffd439de0c2de68b90d17f0a80f4505c02ff4a01392ca48d3753a40deb02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: daf3e270e3e108f60d808f1af5fb85386d8c42ffb6f9980e16d014f3aab64736 0.600000000000 1879868 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": 1391631, "vin": [ { "gen": { "height": 1391621 } } ], "vout": [ { "amount": 600000000, "target": { "key": "daf3e270e3e108f60d808f1af5fb85386d8c42ffb6f9980e16d014f3aab64736" } } ], "extra": [ 1, 230, 225, 93, 255, 212, 57, 222, 12, 45, 230, 139, 144, 209, 127, 10, 128, 244, 80, 92, 2, 255, 74, 1, 57, 44, 164, 141, 55, 83, 164, 13, 235, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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