Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2067029fd6bc45c3f19da34d4c9a75b37f4b63d9fce93a39ff4b263d3b497078

Tx prefix hash: f7eded257bca8a1bb73fe6b502385879d9c119c0c9e8dc41e6130425f5558401
Tx public key: d66d40f0a2d6e3e532d747196b69a78494ee4048c9587d451bf537060a66ad08
Timestamp: 1785098026 Timestamp [UTC]: 2026-07-26 20:33:46 Age [y:d:h:m:s]: 00:117:00:32:01
Block: 1595753 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 87183 RingCT/type: yes/0
Extra: 01d66d40f0a2d6e3e532d747196b69a78494ee4048c9587d451bf537060a66ad08

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4934c87223344a9972335b6cf6032b82b74ac4f0747fde8c014e07c5b775ea15 0.000600000000 2085771 of 15 <44>

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": 1595763, "vin": [ { "gen": { "height": 1595753 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "4934c87223344a9972335b6cf6032b82b74ac4f0747fde8c014e07c5b775ea15", "view_tag": "44" } } } ], "extra": [ 1, 214, 109, 64, 240, 162, 214, 227, 229, 50, 215, 71, 25, 107, 105, 167, 132, 148, 238, 64, 72, 201, 88, 125, 69, 27, 245, 55, 6, 10, 102, 173, 8 ], "rct_signatures": { "type": 0 } }


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