Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79c2ddafa02e3581f6489ad4e26c1adce929d4e35ee36322700024fd0b6c8a1c

Tx prefix hash: 588321ff498b7a51580f6feeab613dedcf23585a64af8bfe10719bc761af0076
Tx public key: ee3fd4c696a2ae2bec17497dc94edd5e374be26e3b5e4d9f32b4ec5470c5f277
Timestamp: 1750709825 Timestamp [UTC]: 2025-06-23 20:17:05 Age [y:d:h:m:s]: 01:146:11:18:17
Block: 1311335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368896 RingCT/type: yes/0
Extra: 01ee3fd4c696a2ae2bec17497dc94edd5e374be26e3b5e4d9f32b4ec5470c5f27702110000000543846d66000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 66e7531e7e9428c6384ba2012763a738501d151f55f59304533368442f2beee5 0.000600000000 1798962 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": 1311345, "vin": [ { "gen": { "height": 1311335 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66e7531e7e9428c6384ba2012763a738501d151f55f59304533368442f2beee5" } } ], "extra": [ 1, 238, 63, 212, 198, 150, 162, 174, 43, 236, 23, 73, 125, 201, 78, 221, 94, 55, 75, 226, 110, 59, 94, 77, 159, 50, 180, 236, 84, 112, 197, 242, 119, 2, 17, 0, 0, 0, 5, 67, 132, 109, 102, 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: