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: 3c200d29ed1fae30e0e3662d395c4f13ee8bd6ee190dd44e81fbe4d11f7ab336
Tx prefix hash: afc8f1a175b840c048e6e260a414178078e5e7f7ecb388e4aa5ebfa5aa9daec4
Tx public key: 1b456a7c818ed9a9080af8fe27af4d3adb6f55fdd63642734a1d7054c2ea86a3
| Timestamp: 1780689886 | Timestamp [UTC]: 2026-06-05 20:04:46 | Age [y:d:h:m:s]: 00:003:07:34:04 |
| Block: 5627 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2320 | RingCT/type: yes/0 |
| Extra: 011b456a7c818ed9a9080af8fe27af4d3adb6f55fdd63642734a1d7054c2ea86a3020900000001e49593ff00 | ||
1 output(s) for total of 34.808835757492 HMNY
| stealth address | amount | amount idx | tag |
| 00: 270f4fb375576c1cc942984f3d8c12404ea5c159a28ce89d86cd3991972decf9 | 34.808835757492 | 7074 of 0 | <88> |
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": 5687,
"vin": [ {
"gen": {
"height": 5627
}
}
],
"vout": [ {
"amount": 34808835757492,
"target": {
"tagged_key": {
"key": "270f4fb375576c1cc942984f3d8c12404ea5c159a28ce89d86cd3991972decf9",
"view_tag": "88"
}
}
}
],
"extra": [ 1, 27, 69, 106, 124, 129, 142, 217, 169, 8, 10, 248, 254, 39, 175, 77, 58, 219, 111, 85, 253, 214, 54, 66, 115, 74, 29, 112, 84, 194, 234, 134, 163, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}