Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a806df1ea3bc8f0f53823c669eef9f851e2abcbdffb30e35d4ee7d522e8ba2aa

Tx prefix hash: 0619d7c8f4aa2fe0ab3f5367d75a02b5123ca0d26ecc528d8ef328e14cfa0700
Tx public key: 3294d2b25b1008458140bfe01448a6788e0d4630a5aa33edb2968f3e0e3ce983
Timestamp: 1747818155 Timestamp [UTC]: 2025-05-21 09:02:35 Age [y:d:h:m:s]: 01:181:18:15:47
Block: 1287651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393950 RingCT/type: yes/0
Extra: 013294d2b25b1008458140bfe01448a6788e0d4630a5aa33edb2968f3e0e3ce9830211000000021f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 342c1ff635b6c9a1e71f06080b43cc7b62c00c79ec6b3097a5352855e03926f5 0.000600000000 1775118 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": 1287661, "vin": [ { "gen": { "height": 1287651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "342c1ff635b6c9a1e71f06080b43cc7b62c00c79ec6b3097a5352855e03926f5" } } ], "extra": [ 1, 50, 148, 210, 178, 91, 16, 8, 69, 129, 64, 191, 224, 20, 72, 166, 120, 142, 13, 70, 48, 165, 170, 51, 237, 178, 150, 143, 62, 14, 60, 233, 131, 2, 17, 0, 0, 0, 2, 31, 144, 81, 122, 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: