Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0308f4b2b7459a3e60427a8638a2e8fdc1fb2e363b5036ce1fd063c4bd30feb5

Tx prefix hash: 8350cb8572df12dc0ecd355480d448f937eba0a33ccc41b1217f7e9bb27b61b8
Tx public key: 3cb348c7b6a30fa30b416b7294ffb5b781c6388601d5e25a8887994acc277dce
Timestamp: 1754120004 Timestamp [UTC]: 2025-08-02 07:33:24 Age [y:d:h:m:s]: 01:110:05:31:59
Block: 1338584 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344127 RingCT/type: yes/0
Extra: 013cb348c7b6a30fa30b416b7294ffb5b781c6388601d5e25a8887994acc277dce0211000000022609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 856940ec293055e961c8d7f71528a3c000b4bb966e42583b6cc743bbce75b72f 0.000600000000 1826393 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": 1338594, "vin": [ { "gen": { "height": 1338584 } } ], "vout": [ { "amount": 600000000, "target": { "key": "856940ec293055e961c8d7f71528a3c000b4bb966e42583b6cc743bbce75b72f" } } ], "extra": [ 1, 60, 179, 72, 199, 182, 163, 15, 163, 11, 65, 107, 114, 148, 255, 181, 183, 129, 198, 56, 134, 1, 213, 226, 90, 136, 135, 153, 74, 204, 39, 125, 206, 2, 17, 0, 0, 0, 2, 38, 9, 179, 160, 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: