Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a08d8a6454def5ebb382f927421f0bddc00cf5f2134bbcaca82dfff7a6ed8131

Tx prefix hash: d7e114808d4847b3d7e11b4d2c1d63016cde6fee4d1c10dba20b062e39f159b9
Tx public key: 803f2575c3a5b25e7e569a7ff4f742da23024fb6b40a7992e56a3c5c2b4d7d60
Timestamp: 1789943338 Timestamp [UTC]: 2026-09-20 22:28:58 Age [y:d:h:m:s]: 00:060:18:51:47
Block: 1639942 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 42910 RingCT/type: yes/0
Extra: 01803f2575c3a5b25e7e569a7ff4f742da23024fb6b40a7992e56a3c5c2b4d7d60

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f4f9917c1dd846f9f962dfab9ce10e12d4b666c3ceed775dc820fd720ed851eb 0.000600000000 2129974 of 15 <65>

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 dinastycoin-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": 1639952, "vin": [ { "gen": { "height": 1639942 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "f4f9917c1dd846f9f962dfab9ce10e12d4b666c3ceed775dc820fd720ed851eb", "view_tag": "65" } } } ], "extra": [ 1, 128, 63, 37, 117, 195, 165, 178, 94, 126, 86, 154, 127, 244, 247, 66, 218, 35, 2, 79, 182, 180, 10, 121, 146, 229, 106, 60, 92, 43, 77, 125, 96 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: