Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25f671c17c3f2a674021f53be00ebca72660b7832a7d39464eb47f6fc42406a3

Tx prefix hash: 024996c41fe1aedef6cd2471dea877e4b67fe9b3c14773f23013ccaa0123ed25
Tx public key: caa8a2ef27abb78b15891ed2507aadc9a612232f4f9a25f97026b17236cb3419
Timestamp: 1783235863 Timestamp [UTC]: 2026-07-05 07:17:43 Age [y:d:h:m:s]: 00:136:08:26:03
Block: 1575055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 106166 RingCT/type: yes/0
Extra: 01caa8a2ef27abb78b15891ed2507aadc9a612232f4f9a25f97026b17236cb34190208e10d7f3ef8a68956

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f2b424c28a581c4ba710e44931c534e644f7dfa55ace6b283c603340a591db28 0.000600000000 2065037 of 15 <e0>

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": 1575065, "vin": [ { "gen": { "height": 1575055 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "f2b424c28a581c4ba710e44931c534e644f7dfa55ace6b283c603340a591db28", "view_tag": "e0" } } } ], "extra": [ 1, 202, 168, 162, 239, 39, 171, 183, 139, 21, 137, 30, 210, 80, 122, 173, 201, 166, 18, 35, 47, 79, 154, 37, 249, 112, 38, 177, 114, 54, 203, 52, 25, 2, 8, 225, 13, 127, 62, 248, 166, 137, 86 ], "rct_signatures": { "type": 0 } }


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