Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4ecc9703973db9111437eb6ed74756193a202efdf48c4b7bd64d480c2af5ce2

Tx prefix hash: 70f0f4bab3b25fb84e7c51a52ef455fc71dac7c045dcde7e6c84c5a11252561d
Tx public key: f68c138bd0b09336ce4ee516ac06069ba085551268a50aff236cda746c03ea15
Timestamp: 1771001495 Timestamp [UTC]: 2026-02-13 16:51:35 Age [y:d:h:m:s]: 00:275:12:10:07
Block: 1477033 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202381 RingCT/type: yes/0
Extra: 01f68c138bd0b09336ce4ee516ac06069ba085551268a50aff236cda746c03ea15021100000001f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 05e9e38a772b5513f2e33ac4744f0f12c76916558907af3a9f97fedafdc2aba6 0.000600000000 1966345 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": 1477043, "vin": [ { "gen": { "height": 1477033 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05e9e38a772b5513f2e33ac4744f0f12c76916558907af3a9f97fedafdc2aba6" } } ], "extra": [ 1, 246, 140, 19, 139, 208, 176, 147, 54, 206, 78, 229, 22, 172, 6, 6, 155, 160, 133, 85, 18, 104, 165, 10, 255, 35, 108, 218, 116, 108, 3, 234, 21, 2, 17, 0, 0, 0, 1, 241, 136, 200, 168, 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: