Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 819f02fdb976b2053b891261ba6ec0040024d963eff218cfb5f714a804e924fd

Tx prefix hash: cbb561707da6a16109253f502ee478d612b50f9ae28d5fc6beb8a2a8afb74e5f
Tx public key: 686185c14e7269273c6c0097c78bbe81e654368295daac349d51b4b33d52aace
Timestamp: 1743698694 Timestamp [UTC]: 2025-04-03 16:44:54 Age [y:d:h:m:s]: 01:095:04:00:06
Block: 1253531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323501 RingCT/type: yes/0
Extra: 01686185c14e7269273c6c0097c78bbe81e654368295daac349d51b4b33d52aace021100000007a2ed016b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 167cc42f69d1db0a7d35812196ec1b1287b09ce7749f9d9414b1cd0faafd703c 0.000600000000 1740612 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": 1253541, "vin": [ { "gen": { "height": 1253531 } } ], "vout": [ { "amount": 600000000, "target": { "key": "167cc42f69d1db0a7d35812196ec1b1287b09ce7749f9d9414b1cd0faafd703c" } } ], "extra": [ 1, 104, 97, 133, 193, 78, 114, 105, 39, 60, 108, 0, 151, 199, 139, 190, 129, 230, 84, 54, 130, 149, 218, 172, 52, 157, 81, 180, 179, 61, 82, 170, 206, 2, 17, 0, 0, 0, 7, 162, 237, 1, 107, 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: