Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 993864f0f5f42c21706539804aa6f0dafdc35f49dbf7a19ae1ec8cea11a7ea38

Tx prefix hash: 42d1cbc44132e8da1e71c31774afeab706f88f190c68c5639e0b7dc90ec0b822
Tx public key: 68d083501fb471d7f2e9c1e128d339a2105def619300886dfc66f9217b09e14a
Timestamp: 1793239318 Timestamp [UTC]: 2026-10-29 02:01:58 Age [y:d:h:m:s]: 00:021:06:22:26
Block: 1664948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 16806 RingCT/type: yes/0
Extra: 0168d083501fb471d7f2e9c1e128d339a2105def619300886dfc66f9217b09e14a

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 396784ed60a83b7dd3b178574acb1f0c16cbd95fea681961aa46d69abb600e7e 0.000600000000 2155706 of 15 <7f>

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": 1664958, "vin": [ { "gen": { "height": 1664948 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "396784ed60a83b7dd3b178574acb1f0c16cbd95fea681961aa46d69abb600e7e", "view_tag": "7f" } } } ], "extra": [ 1, 104, 208, 131, 80, 31, 180, 113, 215, 242, 233, 193, 225, 40, 211, 57, 162, 16, 93, 239, 97, 147, 0, 136, 109, 252, 102, 249, 33, 123, 9, 225, 74 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: