Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3a330002df0dbf89c03cbf761bdd8cd434fcbae11b5e232c2335f32bb438745

Tx prefix hash: 997d39e718817231a0fa8c89f652f5544ab0ae1607150f5871b48c8bef3d79dd
Tx public key: a46f2f6258c96a5ec17605d289ca34a092e02a7320f53b76d05443908cb7760b
Timestamp: 1775125128 Timestamp [UTC]: 2026-04-02 10:18:48 Age [y:d:h:m:s]: 00:226:18:46:43
Block: 1511155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167499 RingCT/type: yes/0
Extra: 01a46f2f6258c96a5ec17605d289ca34a092e02a7320f53b76d05443908cb7760b021100000001ee4b7181000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d5ee810e248330b526de6a2de6e337fd36cb11b08fb25eb352a8296a0fbdf691 0.000600000000 2000945 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": 1511165, "vin": [ { "gen": { "height": 1511155 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5ee810e248330b526de6a2de6e337fd36cb11b08fb25eb352a8296a0fbdf691" } } ], "extra": [ 1, 164, 111, 47, 98, 88, 201, 106, 94, 193, 118, 5, 210, 137, 202, 52, 160, 146, 224, 42, 115, 32, 245, 59, 118, 208, 84, 67, 144, 140, 183, 118, 11, 2, 17, 0, 0, 0, 1, 238, 75, 113, 129, 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: