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: d1f9e4131856e20e5bd5d9b657b1f8b61ac50e9c0c1e59cfd2a06b46b5819e3a
Tx prefix hash: 8e49b82f8de9298a7b1ca0b339b09d116c9220bf82f59445c1611d282b932d9c
Tx public key: 50cbda49ac89fb5ae98628f9e44411fdc4f8f5a18ab3935f256b31b5dcb0f2fd
| Timestamp: 1779781420 | Timestamp [UTC]: 2026-05-26 07:43:40 | Age [y:d:h:m:s]: 00:013:19:06:08 |
| Block: 2109 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5811 | RingCT/type: yes/0 |
| Extra: 0150cbda49ac89fb5ae98628f9e44411fdc4f8f5a18ab3935f256b31b5dcb0f2fd02090000000226697be300 | ||
1 output(s) for total of 35.043190482987 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3b7c65823f22f5485419cae48060c5df95158e52f15ebfa908626c7901c1b7b9 | 35.043190482987 | 2429 of 0 | <f4> |
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": 2169,
"vin": [ {
"gen": {
"height": 2109
}
}
],
"vout": [ {
"amount": 35043190482987,
"target": {
"tagged_key": {
"key": "3b7c65823f22f5485419cae48060c5df95158e52f15ebfa908626c7901c1b7b9",
"view_tag": "f4"
}
}
}
],
"extra": [ 1, 80, 203, 218, 73, 172, 137, 251, 90, 233, 134, 40, 249, 228, 68, 17, 253, 196, 248, 245, 161, 138, 179, 147, 95, 37, 107, 49, 181, 220, 176, 242, 253, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}