Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 695c256bebe3763b9faeccde503b5bef131a88c1dda56c5de6fa7431ca2b7793

Tx prefix hash: ba9d89157c67dd19cf4145447adbb726fafc7260deb145bd1675688be2e986ee
Tx public key: 46ba7b87252d15e5f9f664b7ab8c2a11192e3045f761e0c076aed652dc3020fb
Timestamp: 1785226969 Timestamp [UTC]: 2026-07-28 08:22:49 Age [y:d:h:m:s]: 00:116:16:21:34
Block: 1600168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 83326 RingCT/type: yes/0
Extra: 0146ba7b87252d15e5f9f664b7ab8c2a11192e3045f761e0c076aed652dc3020fb

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d0772c22e73b33d6b199d0e74b2d9fb7e92e699579aa6e1f2711a6b3da366253 0.000600000000 2090186 of 15 <9f>

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": 1600178, "vin": [ { "gen": { "height": 1600168 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "d0772c22e73b33d6b199d0e74b2d9fb7e92e699579aa6e1f2711a6b3da366253", "view_tag": "9f" } } } ], "extra": [ 1, 70, 186, 123, 135, 37, 45, 21, 229, 249, 246, 100, 183, 171, 140, 42, 17, 25, 46, 48, 69, 247, 97, 224, 192, 118, 174, 214, 82, 220, 48, 32, 251 ], "rct_signatures": { "type": 0 } }


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