Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5af58c49c878a2ed0cc88778bc9e69cfe281134c8c9d7d044b5a655d5c20599e

Tx prefix hash: 0f7d3863f1651876dcc8b87812de548841dcdc5978c40b1eabff64248a29f964
Tx public key: 3ae2c342b587b3d5294730f531151fe5ccf837ec4d5558165c9b0fb3b6ef5ef5
Timestamp: 1770194918 Timestamp [UTC]: 2026-02-04 08:48:38 Age [y:d:h:m:s]: 00:286:06:33:56
Block: 1470398 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210065 RingCT/type: yes/0
Extra: 013ae2c342b587b3d5294730f531151fe5ccf837ec4d5558165c9b0fb3b6ef5ef5021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c598e64237a9ce24d8869062eae8b1ab802820a0c18144e0dd07a2d9e339b936 0.000600000000 1959666 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": 1470408, "vin": [ { "gen": { "height": 1470398 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c598e64237a9ce24d8869062eae8b1ab802820a0c18144e0dd07a2d9e339b936" } } ], "extra": [ 1, 58, 226, 195, 66, 181, 135, 179, 213, 41, 71, 48, 245, 49, 21, 31, 229, 204, 248, 55, 236, 77, 85, 88, 22, 92, 155, 15, 179, 182, 239, 94, 245, 2, 17, 0, 0, 0, 3, 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: