Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb34d82f5d453b82659e6cbb3b14d9eb784342ba1edc612bb6cf33161e2fa38e

Tx prefix hash: 018942858cbc9374ce84f9fb31043bc0d80cec3a135ff7dca4ecf2b10e8fc432
Tx public key: e5b7e8c2535b4c35bf03e4643ece23c26d9a0dfd6fefe7623dd4f20b4824aea7
Timestamp: 1759306078 Timestamp [UTC]: 2025-10-01 08:07:58 Age [y:d:h:m:s]: 01:045:18:15:25
Block: 1380300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299029 RingCT/type: yes/0
Extra: 01e5b7e8c2535b4c35bf03e4643ece23c26d9a0dfd6fefe7623dd4f20b4824aea7021100000001d8e7d241000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c2d01b705de59cf73e5bea54509ddc4e5c636ed76eacd31addcaa2ef5ae039f6 0.000600000000 1868411 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": 1380310, "vin": [ { "gen": { "height": 1380300 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2d01b705de59cf73e5bea54509ddc4e5c636ed76eacd31addcaa2ef5ae039f6" } } ], "extra": [ 1, 229, 183, 232, 194, 83, 91, 76, 53, 191, 3, 228, 100, 62, 206, 35, 194, 109, 154, 13, 253, 111, 239, 231, 98, 61, 212, 242, 11, 72, 36, 174, 167, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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: