Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65f71ff06e4d315ca49e2f12c2cbdb6f8a2034867a97449d6d321410e08d3a0f

Tx prefix hash: 2e3e7cfc367ab62d7708bb456bf12c5ed78229083c57d906c06afa1a8beb23e9
Tx public key: fdfeba69f8f3cd3a8a635f436b12a43ac4a4fc56c22123ba98107391aeee2289
Timestamp: 1746965665 Timestamp [UTC]: 2025-05-11 12:14:25 Age [y:d:h:m:s]: 01:190:11:05:58
Block: 1280586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400129 RingCT/type: yes/0
Extra: 01fdfeba69f8f3cd3a8a635f436b12a43ac4a4fc56c22123ba98107391aeee228902110000000d9f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 3243730b48043218711eb222520f8f6bfc848d1a6ff51850b5b1184a1964fb41 0.000600000000 1767975 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": 1280596, "vin": [ { "gen": { "height": 1280586 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3243730b48043218711eb222520f8f6bfc848d1a6ff51850b5b1184a1964fb41" } } ], "extra": [ 1, 253, 254, 186, 105, 248, 243, 205, 58, 138, 99, 95, 67, 107, 18, 164, 58, 196, 164, 252, 86, 194, 33, 35, 186, 152, 16, 115, 145, 174, 238, 34, 137, 2, 17, 0, 0, 0, 13, 159, 159, 230, 140, 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: