Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0e62c57b19c8fb4d375adfbbc1a5457cdf292216be5e5cc2d0d24199c7fe696

Tx prefix hash: 795c0c923098e6768f41b8a5619bde246550b5b007fccee86270779739ba35ec
Tx public key: 31226d310c9f266eba7af69856d39e19731fb15f35dc56923ff91c1c75580e96
Timestamp: 1760454358 Timestamp [UTC]: 2025-10-14 15:05:58 Age [y:d:h:m:s]: 01:034:08:28:44
Block: 1389821 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290903 RingCT/type: yes/0
Extra: 0131226d310c9f266eba7af69856d39e19731fb15f35dc56923ff91c1c75580e960211000000018368266d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 943b28f6d246e7f625cb5d1bf6a0c81341e94994ce033770993b9d91c8037f28 0.000600000000 1878050 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": 1389831, "vin": [ { "gen": { "height": 1389821 } } ], "vout": [ { "amount": 600000000, "target": { "key": "943b28f6d246e7f625cb5d1bf6a0c81341e94994ce033770993b9d91c8037f28" } } ], "extra": [ 1, 49, 34, 109, 49, 12, 159, 38, 110, 186, 122, 246, 152, 86, 211, 158, 25, 115, 31, 177, 95, 53, 220, 86, 146, 63, 249, 28, 28, 117, 88, 14, 150, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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: