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: 25adc4c58b21a9ba53f8c772669b349f955f947487d9c78c1188c93f708b7274
Tx prefix hash: d509bb9d1277f076cfb5e9152e3492a46c4cd1c3f4cefd233e87735d41e533ab
Tx public key: 97c7f3b79fee60cb9b66b53399f973e8552e169d4b11b0f59c032ba8e5fdc552
| Timestamp: 1780834127 | Timestamp [UTC]: 2026-06-07 12:08:47 | Age [y:d:h:m:s]: 00:001:11:10:06 |
| Block: 7381 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 505 | RingCT/type: yes/0 |
| Extra: 0197c7f3b79fee60cb9b66b53399f973e8552e169d4b11b0f59c032ba8e5fdc552020900000004e49593ff00 | ||
1 output(s) for total of 34.692577630622 HMNY
| stealth address | amount | amount idx | tag |
| 00: f185b5e40f1e066ae17607f8bbe39c50117046708e44f50772ff793470232b37 | 34.692577630622 | 9087 of 0 | <6a> |
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": 7441,
"vin": [ {
"gen": {
"height": 7381
}
}
],
"vout": [ {
"amount": 34692577630622,
"target": {
"tagged_key": {
"key": "f185b5e40f1e066ae17607f8bbe39c50117046708e44f50772ff793470232b37",
"view_tag": "6a"
}
}
}
],
"extra": [ 1, 151, 199, 243, 183, 159, 238, 96, 203, 155, 102, 181, 51, 153, 249, 115, 232, 85, 46, 22, 157, 75, 17, 176, 245, 156, 3, 43, 168, 229, 253, 197, 82, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}