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: 5e5ca7f80e3918c8c72ccb69477bcbdd25c93c60c680925b696c7951fc945ff4
Tx prefix hash: 098629f791429b9991c9b59fc643dc77bc6bb0f1c41a9198fd5e31c885626fbd
Tx public key: 63d8ac15bce43fa2ad289fef029843819c8e00929b42b0a1699ab9bc9f14a7c0
| Timestamp: 1780763392 | Timestamp [UTC]: 2026-06-06 16:29:52 | Age [y:d:h:m:s]: 00:002:11:08:58 |
| Block: 6595 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1347 | RingCT/type: yes/0 |
| Extra: 0163d8ac15bce43fa2ad289fef029843819c8e00929b42b0a1699ab9bc9f14a7c0020900000001e49593ff00 | ||
1 output(s) for total of 34.752054966713 HMNY
| stealth address | amount | amount idx | tag |
| 00: fd29f41e3cfabd5b708af82e8073da135e6bdb93f90e22736bf61a5dd823dd3d | 34.752054966713 | 8123 of 0 | <e2> |
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": 6655,
"vin": [ {
"gen": {
"height": 6595
}
}
],
"vout": [ {
"amount": 34752054966713,
"target": {
"tagged_key": {
"key": "fd29f41e3cfabd5b708af82e8073da135e6bdb93f90e22736bf61a5dd823dd3d",
"view_tag": "e2"
}
}
}
],
"extra": [ 1, 99, 216, 172, 21, 188, 228, 63, 162, 173, 40, 159, 239, 2, 152, 67, 129, 156, 142, 0, 146, 155, 66, 176, 161, 105, 154, 185, 188, 159, 20, 167, 192, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}