Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b80e5ba5608e036a2f0690bf490634d2917ed8c2f9f180c6ec930647b46c8f0

Tx prefix hash: 18ddb0b6ba680717368abd9dacd3846ca0d82e3c5f4c7e3fb08d2a8cdafd8406
Tx public key: 839aaf3ac07f4bc13a584fceb705f165f615a873c58d4c34f7f3d3daa2bd48d4
Timestamp: 1743418855 Timestamp [UTC]: 2025-03-31 11:00:55 Age [y:d:h:m:s]: 01:235:14:20:01
Block: 1251218 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 432276 RingCT/type: yes/0
Extra: 01839aaf3ac07f4bc13a584fceb705f165f615a873c58d4c34f7f3d3daa2bd48d4021100000004703241eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: de097f6786f391fdd2e8ab09527c26ebe6c1fa86b12cb2f057f102aa95ba6158 0.000600000000 1738279 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 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": 1251228, "vin": [ { "gen": { "height": 1251218 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de097f6786f391fdd2e8ab09527c26ebe6c1fa86b12cb2f057f102aa95ba6158" } } ], "extra": [ 1, 131, 154, 175, 58, 192, 127, 75, 193, 58, 88, 79, 206, 183, 5, 241, 101, 246, 21, 168, 115, 197, 141, 76, 52, 247, 243, 211, 218, 162, 189, 72, 212, 2, 17, 0, 0, 0, 4, 112, 50, 65, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


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