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: 02388e4b772dbb11fa7ce7a88bdf9f4cc6236fa5584c298d69cca9b0183b4b9e
Tx prefix hash: f5cec910b513cea103d2eaf1d2882959c3fcdaf6cd4e6962ebe5ae2ff42c4bb5
Tx public key: cd0fb6c26e9e47ce98152892a29ef876793189ad2ef23957d056d554c57fd36f
| Timestamp: 1780768041 | Timestamp [UTC]: 2026-06-06 17:47:21 | Age [y:d:h:m:s]: 00:002:07:48:36 |
| Block: 6637 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1249 | RingCT/type: yes/0 |
| Extra: 01cd0fb6c26e9e47ce98152892a29ef876793189ad2ef23957d056d554c57fd36f020900000002e49593ff00 | ||
1 output(s) for total of 34.741843730638 HMNY
| stealth address | amount | amount idx | tag |
| 00: 361b9ed1e700335a577fa0bfc2a588be298b92ed3527ded2e6986b7327422dff | 34.741843730638 | 8181 of 0 | <8e> |
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": 6697,
"vin": [ {
"gen": {
"height": 6637
}
}
],
"vout": [ {
"amount": 34741843730638,
"target": {
"tagged_key": {
"key": "361b9ed1e700335a577fa0bfc2a588be298b92ed3527ded2e6986b7327422dff",
"view_tag": "8e"
}
}
}
],
"extra": [ 1, 205, 15, 182, 194, 110, 158, 71, 206, 152, 21, 40, 146, 162, 158, 248, 118, 121, 49, 137, 173, 46, 242, 57, 87, 208, 86, 213, 84, 197, 127, 211, 111, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}