Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c65f747e2cfc71941174eaeeecc216a89419d263d1423edf928afd0167d80cbe

Tx prefix hash: 0f0febce3a2a3a1cd567d1bd384d7c65e5262c600ebc568d69be057578178943
Tx public key: bae8311dfd0f6fdd5fd009e105fbcb2c2593f8b543489133679d0688f58efbc8
Timestamp: 1773904676 Timestamp [UTC]: 2026-03-19 07:17:56 Age [y:d:h:m:s]: 00:240:18:19:03
Block: 1501051 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177485 RingCT/type: yes/0
Extra: 01bae8311dfd0f6fdd5fd009e105fbcb2c2593f8b543489133679d0688f58efbc8021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5f8a6bb853d26506630997486f6cdec2ea910bf31f7943a9f736d25434480f14 0.000600000000 1990729 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": 1501061, "vin": [ { "gen": { "height": 1501051 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f8a6bb853d26506630997486f6cdec2ea910bf31f7943a9f736d25434480f14" } } ], "extra": [ 1, 186, 232, 49, 29, 253, 15, 111, 221, 95, 208, 9, 225, 5, 251, 203, 44, 37, 147, 248, 181, 67, 72, 145, 51, 103, 157, 6, 136, 245, 142, 251, 200, 2, 17, 0, 0, 0, 3, 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: