Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22fdca9f448f08d8e140c5a5d5c2b232fe9d1894e467e73dcb386cec6d6323e5

Tx prefix hash: 2373b969f868afdd4723c2ef229e28b43b0f3027382b53d92e15bcbd25ea0844
Tx public key: 2b8ca80254560ca7545b040939627ec583a1f93557e2e6a33d7d143ea2838606
Timestamp: 1783279672 Timestamp [UTC]: 2026-07-05 19:27:52 Age [y:d:h:m:s]: 00:132:02:52:31
Block: 1575443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 102994 RingCT/type: yes/0
Extra: 012b8ca80254560ca7545b040939627ec583a1f93557e2e6a33d7d143ea283860602083dd245b1428cbbcb

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7e299c89c17d9b2f870c2df0f77cf218817d2f4d7d1e0d9a5d7bc39eb7381bdd 0.000600000000 2065425 of 15 <55>

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": 1575453, "vin": [ { "gen": { "height": 1575443 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "7e299c89c17d9b2f870c2df0f77cf218817d2f4d7d1e0d9a5d7bc39eb7381bdd", "view_tag": "55" } } } ], "extra": [ 1, 43, 140, 168, 2, 84, 86, 12, 167, 84, 91, 4, 9, 57, 98, 126, 197, 131, 161, 249, 53, 87, 226, 230, 163, 61, 125, 20, 62, 162, 131, 134, 6, 2, 8, 61, 210, 69, 177, 66, 140, 187, 203 ], "rct_signatures": { "type": 0 } }


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