Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5f11c2c35a36757eb5eefbde07ea808742bc50ca3a09e24725bd808b71908f0

Tx prefix hash: 0f3463f0f029cf956c6ce752580372a46b6bc2e3be1b315b9f0760890086b9fa
Tx public key: 67335f28bf6b7a065a096d26d11528689c7428cd91bd9001f3efe3438456ea2b
Timestamp: 1759425652 Timestamp [UTC]: 2025-10-02 17:20:52 Age [y:d:h:m:s]: 01:043:05:24:38
Block: 1381289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297171 RingCT/type: yes/0
Extra: 0167335f28bf6b7a065a096d26d11528689c7428cd91bd9001f3efe3438456ea2b021100000004a5dccd79000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: edea8496a68d642a31eec833fc1c2a5ca65f842d8275e310e96113d7e8bc588e 0.000600000000 1869408 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": 1381299, "vin": [ { "gen": { "height": 1381289 } } ], "vout": [ { "amount": 600000000, "target": { "key": "edea8496a68d642a31eec833fc1c2a5ca65f842d8275e310e96113d7e8bc588e" } } ], "extra": [ 1, 103, 51, 95, 40, 191, 107, 122, 6, 90, 9, 109, 38, 209, 21, 40, 104, 156, 116, 40, 205, 145, 189, 144, 1, 243, 239, 227, 67, 132, 86, 234, 43, 2, 17, 0, 0, 0, 4, 165, 220, 205, 121, 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: