Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f42b52ea0682674fa3565cd5a596dc034cf4f5728cbd0d17d240ad580e43c8b1

Tx prefix hash: 688da5c011a3d0d506bf94151446552c6990fe85e70de775bbd15029977f6883
Tx public key: 4fd3114ddc1460ce8ccfc883beb8834ffd19c02a902349d3c24e5018b1c0f310
Timestamp: 1757551774 Timestamp [UTC]: 2025-09-11 00:49:34 Age [y:d:h:m:s]: 01:070:20:47:34
Block: 1365779 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317175 RingCT/type: yes/0
Extra: 014fd3114ddc1460ce8ccfc883beb8834ffd19c02a902349d3c24e5018b1c0f310021100000004ad7948d0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2c2e2af78654e0ebba553254df23dfcc191d6f817729db91e8d371b9934b810d 0.000600000000 1853818 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": 1365789, "vin": [ { "gen": { "height": 1365779 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c2e2af78654e0ebba553254df23dfcc191d6f817729db91e8d371b9934b810d" } } ], "extra": [ 1, 79, 211, 17, 77, 220, 20, 96, 206, 140, 207, 200, 131, 190, 184, 131, 79, 253, 25, 192, 42, 144, 35, 73, 211, 194, 78, 80, 24, 177, 192, 243, 16, 2, 17, 0, 0, 0, 4, 173, 121, 72, 208, 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: