Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c3224f0f5e72068f448c9727e5de08ac073dff356b7c6d36b5c75ead0909a26

Tx prefix hash: 50bb722294946d2f765ba961924f006ab443961df972a392f216e27177b95ee2
Tx public key: f7fa436faa3530915eba354518f8bce476933496e5a585ee56e0d3d5e57124d0
Timestamp: 1773267535 Timestamp [UTC]: 2026-03-11 22:18:55 Age [y:d:h:m:s]: 00:252:11:13:44
Block: 1495794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185997 RingCT/type: yes/0
Extra: 01f7fa436faa3530915eba354518f8bce476933496e5a585ee56e0d3d5e57124d0021100000004f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 062a169c08cb00796b6e631c2f92f2afaaf12a5ffaa0867c0acb6b12b4017418 0.000600000000 1985408 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": 1495804, "vin": [ { "gen": { "height": 1495794 } } ], "vout": [ { "amount": 600000000, "target": { "key": "062a169c08cb00796b6e631c2f92f2afaaf12a5ffaa0867c0acb6b12b4017418" } } ], "extra": [ 1, 247, 250, 67, 111, 170, 53, 48, 145, 94, 186, 53, 69, 24, 248, 188, 228, 118, 147, 52, 150, 229, 165, 133, 238, 86, 224, 211, 213, 229, 113, 36, 208, 2, 17, 0, 0, 0, 4, 241, 136, 200, 168, 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: