Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a207f4ce21509d2477ca799e8b16079c71469bf55fee5715dcbd5eb0d5b15ce

Tx prefix hash: 92f13ac87dd04d2765fc43977cca4cfefcedf4806dbb3acc38ec980cf29433a3
Tx public key: 4c8cb0bdb401ca7a871d541be5682c15cf8b3003ff6bcc2e7c1cf5e33a469e22
Timestamp: 1771679358 Timestamp [UTC]: 2026-02-21 13:09:18 Age [y:d:h:m:s]: 00:270:11:05:05
Block: 1482651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198848 RingCT/type: yes/0
Extra: 014c8cb0bdb401ca7a871d541be5682c15cf8b3003ff6bcc2e7c1cf5e33a469e22021100000009e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 606f3dc5fc5f3a2af4d41a39620dadfa0d9868c2b0a09e8ec27fd35de4652239 0.000600000000 1972045 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": 1482661, "vin": [ { "gen": { "height": 1482651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "606f3dc5fc5f3a2af4d41a39620dadfa0d9868c2b0a09e8ec27fd35de4652239" } } ], "extra": [ 1, 76, 140, 176, 189, 180, 1, 202, 122, 135, 29, 84, 27, 229, 104, 44, 21, 207, 139, 48, 3, 255, 107, 204, 46, 124, 28, 245, 227, 58, 70, 158, 34, 2, 17, 0, 0, 0, 9, 228, 245, 25, 63, 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: