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: 8aaa797eef02644394270b43d024c4d350acb49853237db25b4b373c8f6719d0
Tx prefix hash: 78a4a7e2c4673ea3244c3dc98e41fa8a4edf5f6f4af32c9beb7f6772120c8dc3
Tx public key: e08736382086f9ee13bb8e805c8215b6900a3c96b3fab85d8d9362260776bb53
| Timestamp: 1780044553 | Timestamp [UTC]: 2026-05-29 08:49:13 | Age [y:d:h:m:s]: 00:010:16:46:44 |
| Block: 4329 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3557 | RingCT/type: yes/0 |
| Extra: 01e08736382086f9ee13bb8e805c8215b6900a3c96b3fab85d8d9362260776bb5302090000000126697be300 | ||
1 output(s) for total of 34.895120180251 HMNY
| stealth address | amount | amount idx | tag |
| 00: ee0959c720abc01d9b4667272d628edfdea8df30077d91848f271b6c2749120e | 34.895120180251 | 5411 of 0 | <87> |
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": 4389,
"vin": [ {
"gen": {
"height": 4329
}
}
],
"vout": [ {
"amount": 34895120180251,
"target": {
"tagged_key": {
"key": "ee0959c720abc01d9b4667272d628edfdea8df30077d91848f271b6c2749120e",
"view_tag": "87"
}
}
}
],
"extra": [ 1, 224, 135, 54, 56, 32, 134, 249, 238, 19, 187, 142, 128, 92, 130, 21, 182, 144, 10, 60, 150, 179, 250, 184, 93, 141, 147, 98, 38, 7, 118, 187, 83, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}