Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 895d5bb45df87ca324f70eced5251a7d8a4b2d5f6d6a1ddabf27a800358f07f4

Tx prefix hash: a9f81a5a05a46cee461aa26d886f8d45d41695698a7ad7c62c71aefe4f18203b
Tx public key: 6cb0d9f22cdf2b47a9db15f62bdd1a486e468ca2d465992ffc6955ddabd4922c
Timestamp: 1752334148 Timestamp [UTC]: 2025-07-12 15:29:08 Age [y:d:h:m:s]: 01:125:15:28:21
Block: 1323993 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354724 RingCT/type: yes/0
Extra: 016cb0d9f22cdf2b47a9db15f62bdd1a486e468ca2d465992ffc6955ddabd4922c0211000000018368266d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 06942cfe5e2ffac1ad308fcf61aa55077c05865c0b57bda5a995816475da7aa8 0.000600000000 1811736 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": 1324003, "vin": [ { "gen": { "height": 1323993 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06942cfe5e2ffac1ad308fcf61aa55077c05865c0b57bda5a995816475da7aa8" } } ], "extra": [ 1, 108, 176, 217, 242, 44, 223, 43, 71, 169, 219, 21, 246, 43, 221, 26, 72, 110, 70, 140, 162, 212, 101, 153, 47, 252, 105, 85, 221, 171, 212, 146, 44, 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: