Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f12253a831df9510e1ed1aef34245d95f212cbef60234ff7570bea825d9cd1e

Tx prefix hash: 2b4405db4b652df39dc20e6fb1cc982aaaef54cfd37780fe26ed7f271caa45c7
Tx public key: 8c036a913e27866ec543d6a7ad6728543d023a91847efe9a78a0d6c760e8df8d
Timestamp: 1742326605 Timestamp [UTC]: 2025-03-18 19:36:45 Age [y:d:h:m:s]: 01:159:05:46:12
Block: 1242197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378144 RingCT/type: yes/0
Extra: 018c036a913e27866ec543d6a7ad6728543d023a91847efe9a78a0d6c760e8df8d0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 250af895fc7dcbb05dd2abf9f7dd0bfeb14f8868406ced1de6a559e812c10554 0.000600000000 1729170 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": 1242207, "vin": [ { "gen": { "height": 1242197 } } ], "vout": [ { "amount": 600000000, "target": { "key": "250af895fc7dcbb05dd2abf9f7dd0bfeb14f8868406ced1de6a559e812c10554" } } ], "extra": [ 1, 140, 3, 106, 145, 62, 39, 134, 110, 197, 67, 214, 167, 173, 103, 40, 84, 61, 2, 58, 145, 132, 126, 254, 154, 120, 160, 214, 199, 96, 232, 223, 141, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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: