Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac801b859f7d8b65810eaeb49aa3e6576072d647de67fa82f83c9ea5d51f7b36

Tx prefix hash: 89cd2fe406f6cb5f2925a87e4642387e0d8bd37fcde649c1f6d248980cd106e5
Tx public key: d20cb33bd222f7e79e669f1bc84bf86047f820d3f910f2cdbc6fa01930ffe139
Timestamp: 1773065049 Timestamp [UTC]: 2026-03-09 14:04:09 Age [y:d:h:m:s]: 00:251:09:26:18
Block: 1494111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185129 RingCT/type: yes/0
Extra: 01d20cb33bd222f7e79e669f1bc84bf86047f820d3f910f2cdbc6fa01930ffe139021100000004e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7af1354aae5d4337379bbabfaaa4e78fc94cec66a1da667a60e8f7c2725fc679 0.000600000000 1983679 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": 1494121, "vin": [ { "gen": { "height": 1494111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7af1354aae5d4337379bbabfaaa4e78fc94cec66a1da667a60e8f7c2725fc679" } } ], "extra": [ 1, 210, 12, 179, 59, 210, 34, 247, 231, 158, 102, 159, 27, 200, 75, 248, 96, 71, 248, 32, 211, 249, 16, 242, 205, 188, 111, 160, 25, 48, 255, 225, 57, 2, 17, 0, 0, 0, 4, 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: