Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 778850c95c82321079e2fcd981b4bcb73c094660d24bf227eeb59d7426d162d0

Tx prefix hash: b8d2f5775bb658d3975cd3ea3af11eca432227fd27fe7870d41b69bb7600403e
Tx public key: 364e5f2d453aff1393d9a6a4c11754a0ba967ce2f1802733f533cd2954504d52
Timestamp: 1765308064 Timestamp [UTC]: 2025-12-09 19:21:04 Age [y:d:h:m:s]: 00:342:05:00:51
Block: 1430040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249978 RingCT/type: yes/0
Extra: 01364e5f2d453aff1393d9a6a4c11754a0ba967ce2f1802733f533cd2954504d5202110000001370609d03000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0cb61008868ea8e17644bdb8683a6cc219a1a033180ada6762d7f85bb079f170 0.000600000000 1918773 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": 1430050, "vin": [ { "gen": { "height": 1430040 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cb61008868ea8e17644bdb8683a6cc219a1a033180ada6762d7f85bb079f170" } } ], "extra": [ 1, 54, 78, 95, 45, 69, 58, 255, 19, 147, 217, 166, 164, 193, 23, 84, 160, 186, 150, 124, 226, 241, 128, 39, 51, 245, 51, 205, 41, 84, 80, 77, 82, 2, 17, 0, 0, 0, 19, 112, 96, 157, 3, 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: