Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 02492145e4c4e0077cfc5ecc1704e48e273c058e69b45594d46fef7fecfcf18c

Tx prefix hash: 8c372e25bfd5c894a4e7f2a61a92b2864f8449d391e55e6a2fd42c326e8a7d64
Tx public key: ea7edd282d30606a818b89a44c9cc2f88abd42c16af020035eda9d8973259a20
Timestamp: 1793639092 Timestamp [UTC]: 2026-11-02 17:04:52 Age [y:d:h:m:s]: 00:016:12:52:34
Block: 1668667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 13016 RingCT/type: yes/0
Extra: 01ea7edd282d30606a818b89a44c9cc2f88abd42c16af020035eda9d8973259a20

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9196c575ca8ac9afbef332adf3c522509e5ca4fad06f94ede94ee39caed097f9 0.000600000000 2159425 of 15 <5d>

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": 1668677, "vin": [ { "gen": { "height": 1668667 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "9196c575ca8ac9afbef332adf3c522509e5ca4fad06f94ede94ee39caed097f9", "view_tag": "5d" } } } ], "extra": [ 1, 234, 126, 221, 40, 45, 48, 96, 106, 129, 139, 137, 164, 76, 156, 194, 248, 138, 189, 66, 193, 106, 240, 32, 3, 94, 218, 157, 137, 115, 37, 154, 32 ], "rct_signatures": { "type": 0 } }


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