For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: 6a88772d3066efe4e371f0815d276d97fa1b124bdbcacd4bd08ae2b0c87373ac
Tx prefix hash: d0b3947e9dec5332a5fe6ffa504457070fe5bb43c5c01f50254d88e96dd68122
Tx public key: 6aa94d9b517df4d3384607bb26ad5ccbec9480ba22ec0ade79cdcd684b4769ad
| Timestamp: 1780986613 | Timestamp [UTC]: 2026-06-09 06:30:13 | Age [y:d:h:m:s]: 00:000:04:56:35 |
| Block: 8154 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 356 | RingCT/type: yes/0 |
| Extra: 016aa94d9b517df4d3384607bb26ad5ccbec9480ba22ec0ade79cdcd684b4769ad020900000001e49593ff00 | ||
1 output(s) for total of 34.656117210998 HMNY
| stealth address | amount | amount idx | tag |
| 00: 257158e515f8cf1cbecfa519fa754021a53b717d5c5c31599fa635bc7aa96618 | 34.656117210998 | 10096 of 0 | <72> |
Check which outputs belong to given HMNY 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 HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-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": 8214,
"vin": [ {
"gen": {
"height": 8154
}
}
],
"vout": [ {
"amount": 34656117210998,
"target": {
"tagged_key": {
"key": "257158e515f8cf1cbecfa519fa754021a53b717d5c5c31599fa635bc7aa96618",
"view_tag": "72"
}
}
}
],
"extra": [ 1, 106, 169, 77, 155, 81, 125, 244, 211, 56, 70, 7, 187, 38, 173, 92, 203, 236, 148, 128, 186, 34, 236, 10, 222, 121, 205, 205, 104, 75, 71, 105, 173, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}