Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81b5ed52a7c8fb81ab7609c7d52d849801a9c46cbe3644fca1be8f122de7408e

Tx prefix hash: 5ce3f5779bb06ae6cb59c184f920ed30156271d5a000b2ed03bdc848efd27081
Tx public key: 937a9fcc83b23ab2f4bb85f67b27c34aa3711a23f46a9c1e89dac69c129a7129
Timestamp: 1750254376 Timestamp [UTC]: 2025-06-18 13:46:16 Age [y:d:h:m:s]: 00:328:13:29:50
Block: 1307683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224869 RingCT/type: yes/0
Extra: 01937a9fcc83b23ab2f4bb85f67b27c34aa3711a23f46a9c1e89dac69c129a712902110000000225a35a0f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 717f76d1d4f7951426f9661d4e3d0b67a2a1ea8d42dbee3341b2babf5f3de517 0.000600000000 1795294 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": 1307693, "vin": [ { "gen": { "height": 1307683 } } ], "vout": [ { "amount": 600000000, "target": { "key": "717f76d1d4f7951426f9661d4e3d0b67a2a1ea8d42dbee3341b2babf5f3de517" } } ], "extra": [ 1, 147, 122, 159, 204, 131, 178, 58, 178, 244, 187, 133, 246, 123, 39, 195, 74, 163, 113, 26, 35, 244, 106, 156, 30, 137, 218, 198, 156, 18, 154, 113, 41, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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: