Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38d89db6f86a96373d56565f03db4bc583db7e2f1a270e3cd2a6abf7905080b3

Tx prefix hash: c06c00d574960b8979748b1c308f04d65b6312a13b60155447a38ece33766717
Tx public key: d8d370149568bc7ca1299ae08838f5aa6aa3bf1a7249594c01898d3113ce871c
Timestamp: 1773498206 Timestamp [UTC]: 2026-03-14 14:23:26 Age [y:d:h:m:s]: 00:247:12:50:56
Block: 1497702 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182403 RingCT/type: yes/0
Extra: 01d8d370149568bc7ca1299ae08838f5aa6aa3bf1a7249594c01898d3113ce871c021100000007e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7f072e6ccbaa77a2cccfd83ff6129c3868e71f5c271d4bcf16684872ff87af31 0.000600000000 1987340 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": 1497712, "vin": [ { "gen": { "height": 1497702 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7f072e6ccbaa77a2cccfd83ff6129c3868e71f5c271d4bcf16684872ff87af31" } } ], "extra": [ 1, 216, 211, 112, 20, 149, 104, 188, 124, 161, 41, 154, 224, 136, 56, 245, 170, 106, 163, 191, 26, 114, 73, 89, 76, 1, 137, 141, 49, 19, 206, 135, 28, 2, 17, 0, 0, 0, 7, 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: