Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cff9c239a24967b698da150e3ff732dfd63246887cbf11fe5d8b057bd4baf8b4

Tx prefix hash: 1a560630dd1d9bcb02212a12702354f42b1276549376f17d36512be0eac02baa
Tx public key: 6393ee4b9c95d1b68e9a4ba69121cdf9a3bf4632657e24ee60c5e8adac23fdae
Timestamp: 1748017061 Timestamp [UTC]: 2025-05-23 16:17:41 Age [y:d:h:m:s]: 01:182:07:01:41
Block: 1289291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394203 RingCT/type: yes/0
Extra: 016393ee4b9c95d1b68e9a4ba69121cdf9a3bf4632657e24ee60c5e8adac23fdae0211000000021f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: afe8454101246b0367e59374bbf29dc79646698854040526c242c5eb3c2bd6e0 0.000600000000 1776758 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": 1289301, "vin": [ { "gen": { "height": 1289291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "afe8454101246b0367e59374bbf29dc79646698854040526c242c5eb3c2bd6e0" } } ], "extra": [ 1, 99, 147, 238, 75, 156, 149, 209, 182, 142, 154, 75, 166, 145, 33, 205, 249, 163, 191, 70, 50, 101, 126, 36, 238, 96, 197, 232, 173, 172, 35, 253, 174, 2, 17, 0, 0, 0, 2, 31, 144, 81, 122, 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: