Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5bd543a07640c9381ec8bc2a1c19b13ccc1fe500f256f11e51a4b6d9b8e5a0b3

Tx prefix hash: a869bed41dcb5fafdc6254c01ab261bacfa12bdaa5c058ffd0c342013c3565c4
Tx public key: 38a15b4d007871beb0e2e3e31e9dfa0ff068daa5d1f8b1c94c44674e338fe5e5
Timestamp: 1759055173 Timestamp [UTC]: 2025-09-28 10:26:13 Age [y:d:h:m:s]: 01:047:21:18:59
Block: 1378223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300523 RingCT/type: yes/0
Extra: 0138a15b4d007871beb0e2e3e31e9dfa0ff068daa5d1f8b1c94c44674e338fe5e5021100000001a5dccd79000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 25680c38ab50d55e0cc8b4637918811176eb7c26269e5b4d8390ca2853f373fc 0.000600000000 1866318 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": 1378233, "vin": [ { "gen": { "height": 1378223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25680c38ab50d55e0cc8b4637918811176eb7c26269e5b4d8390ca2853f373fc" } } ], "extra": [ 1, 56, 161, 91, 77, 0, 120, 113, 190, 176, 226, 227, 227, 30, 157, 250, 15, 240, 104, 218, 165, 209, 248, 177, 201, 76, 68, 103, 78, 51, 143, 229, 229, 2, 17, 0, 0, 0, 1, 165, 220, 205, 121, 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: