Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c9d5a5a8a4c4629a8ecfa48c6667aafcd99074ae6355262a5958fed52c53c6a

Tx prefix hash: b68bb7925e929b6728f2271f1c3df6943e8820253e0d8ba2ddceaae146144cc7
Tx public key: 26c13402604aa2820ce5e6f85d54545a18dfcd73b7f422921c5d81643d9f4739
Timestamp: 1773322084 Timestamp [UTC]: 2026-03-12 13:28:04 Age [y:d:h:m:s]: 00:059:20:30:11
Block: 1496249 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 35280 RingCT/type: yes/0
Extra: 0126c13402604aa2820ce5e6f85d54545a18dfcd73b7f422921c5d81643d9f4739021100000002e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 0ba5965d2c38e746dcd565e64e91a1c7b379fe9d030c54d57fff679c5171a315 0.000600000000 1985871 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": 1496259, "vin": [ { "gen": { "height": 1496249 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ba5965d2c38e746dcd565e64e91a1c7b379fe9d030c54d57fff679c5171a315" } } ], "extra": [ 1, 38, 193, 52, 2, 96, 74, 162, 130, 12, 229, 230, 248, 93, 84, 84, 90, 24, 223, 205, 115, 183, 244, 34, 146, 28, 93, 129, 100, 61, 159, 71, 57, 2, 17, 0, 0, 0, 2, 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: