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: 81787b8fd424fab7e73622c21349309a9a9a77e3148dde2c4dde411bcf02462b
Tx prefix hash: aad480b57bd560c36ec60bb26d38e6bd0c615613adf2b2b8b82e830cf18ad606
Tx public key: d191a7e1d6406f115ad9a6c0aa91462e40fff01ef419895c60bd1a6fadcc51c4
| Timestamp: 1780096776 | Timestamp [UTC]: 2026-05-29 23:19:36 | Age [y:d:h:m:s]: 00:010:02:16:21 |
| Block: 4835 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3051 | RingCT/type: yes/0 |
| Extra: 01d191a7e1d6406f115ad9a6c0aa91462e40fff01ef419895c60bd1a6fadcc51c402090000000c26697be300 | ||
1 output(s) for total of 34.864076871686 HMNY
| stealth address | amount | amount idx | tag |
| 00: f324bb478efe5ea2eb8c27456753436f4b78790880d644eafca895b806f371dc | 34.864076871686 | 6087 of 0 | <67> |
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": 4895,
"vin": [ {
"gen": {
"height": 4835
}
}
],
"vout": [ {
"amount": 34864076871686,
"target": {
"tagged_key": {
"key": "f324bb478efe5ea2eb8c27456753436f4b78790880d644eafca895b806f371dc",
"view_tag": "67"
}
}
}
],
"extra": [ 1, 209, 145, 167, 225, 214, 64, 111, 17, 90, 217, 166, 192, 170, 145, 70, 46, 64, 255, 240, 30, 244, 25, 137, 92, 96, 189, 26, 111, 173, 204, 81, 196, 2, 9, 0, 0, 0, 12, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}