Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65d4b69696574ca035a9f99fce4102cc3e4f637b67cc87bd86245e7565265ce6

Tx prefix hash: a2ee490730ae950be0623b562608d9a3d4604fd3338a6f9f26820733bc2047f8
Tx public key: e87e19ca0953039259e891d066142320f6a8ebc87c9a56238e7e08f6600e1b80
Timestamp: 1581567753 Timestamp [UTC]: 2020-02-13 04:22:33 Age [y:d:h:m:s]: 06:094:23:16:25
Block: 63831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1471745 RingCT/type: yes/0
Extra: 01e87e19ca0953039259e891d066142320f6a8ebc87c9a56238e7e08f6600e1b80021100000001c71d3ff9000000000000000000

1 output(s) for total of 0.377139666081 xmr

stealth address amount amount idx tag
00: 0b7c7d9d28e701170c526a7d226032f9597429bd2654e7fc7c18a80e03661d07 0.377139666081 117675 of 0 -

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": 63841, "vin": [ { "gen": { "height": 63831 } } ], "vout": [ { "amount": 377139666081, "target": { "key": "0b7c7d9d28e701170c526a7d226032f9597429bd2654e7fc7c18a80e03661d07" } } ], "extra": [ 1, 232, 126, 25, 202, 9, 83, 3, 146, 89, 232, 145, 208, 102, 20, 35, 32, 246, 168, 235, 200, 124, 154, 86, 35, 142, 126, 8, 246, 96, 14, 27, 128, 2, 17, 0, 0, 0, 1, 199, 29, 63, 249, 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: