Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 213bf2f4941dbf96da6ee8fed8013393bda0790dda3353863e9b7c4f147e350b

Tx prefix hash: 2f2425e73b30b6079d6cc4dfeef0e88082010fdd743ed43dddc952046139a86f
Tx public key: 26aea0f8107969c10a3648d1de6c0a63e98e50d65f04a42ac9fab127ba32db4f
Timestamp: 1744301209 Timestamp [UTC]: 2025-04-10 16:06:49 Age [y:d:h:m:s]: 01:136:11:45:11
Block: 1258521 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361896 RingCT/type: yes/0
Extra: 0126aea0f8107969c10a3648d1de6c0a63e98e50d65f04a42ac9fab127ba32db4f021100000005dbb571c1000000000000000000

1 output(s) for total of 0.000600010000 xmr

stealth address amount amount idx tag
00: 7efd62a227d32bf67053e9b6db2ec34bece8f835937216bc11b622b971ee3737 0.000600010000 1745654 of 0 -

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": 1258531, "vin": [ { "gen": { "height": 1258521 } } ], "vout": [ { "amount": 600010000, "target": { "key": "7efd62a227d32bf67053e9b6db2ec34bece8f835937216bc11b622b971ee3737" } } ], "extra": [ 1, 38, 174, 160, 248, 16, 121, 105, 193, 10, 54, 72, 209, 222, 108, 10, 99, 233, 142, 80, 214, 95, 4, 164, 42, 201, 250, 177, 39, 186, 50, 219, 79, 2, 17, 0, 0, 0, 5, 219, 181, 113, 193, 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: