Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 342f9b18c102a9691d8be8e2b546895e2c2811a77cdc7270410e568415c2e4c0

Tx prefix hash: 0e5e22180804c4895b0c6ccdf7fd0dcc3e7f18298814f943e2083f5c91d9e63c
Tx public key: 8090460d3a22eb7878d4f51c3c9a8ff6c2c7da8594bb675c2f48fdb1013fbd63
Timestamp: 1774600262 Timestamp [UTC]: 2026-03-27 08:31:02 Age [y:d:h:m:s]: 00:238:01:30:49
Block: 1506812 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175793 RingCT/type: yes/0
Extra: 018090460d3a22eb7878d4f51c3c9a8ff6c2c7da8594bb675c2f48fdb1013fbd63021100000006e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7058d57329f22bbfbfef1025cce163b96a2d4928aa13ba76c368a65cedd5055b 0.000600000000 1996560 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": 1506822, "vin": [ { "gen": { "height": 1506812 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7058d57329f22bbfbfef1025cce163b96a2d4928aa13ba76c368a65cedd5055b" } } ], "extra": [ 1, 128, 144, 70, 13, 58, 34, 235, 120, 120, 212, 245, 28, 60, 154, 143, 246, 194, 199, 218, 133, 148, 187, 103, 92, 47, 72, 253, 177, 1, 63, 189, 99, 2, 17, 0, 0, 0, 6, 228, 245, 25, 63, 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: