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: e1e86513bcc5c25fe8fad6581fe153d0dd6d8846c99e3d136584ad62f85864d8
Tx prefix hash: 49d3f078c37c517919b7639567158f0419ca54f5ca891937cebae0b3b9ff9d14
Tx public key: 46544b3dc53dfca8156488f1080cb0be9f4274ede328d5f3e2bcdc4899a0c55e
| Timestamp: 1779879052 | Timestamp [UTC]: 2026-05-27 10:50:52 | Age [y:d:h:m:s]: 00:012:14:45:05 |
| Block: 2922 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4964 | RingCT/type: yes/0 |
| Extra: 0146544b3dc53dfca8156488f1080cb0be9f4274ede328d5f3e2bcdc4899a0c55e02090000000226697be300 | ||
1 output(s) for total of 34.988891962024 HMNY
| stealth address | amount | amount idx | tag |
| 00: e5155c0c316b18144224f2980e0619be3efbdef87db3bca72da3745b244105c5 | 34.988891962024 | 3464 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": 2982,
"vin": [ {
"gen": {
"height": 2922
}
}
],
"vout": [ {
"amount": 34988891962024,
"target": {
"tagged_key": {
"key": "e5155c0c316b18144224f2980e0619be3efbdef87db3bca72da3745b244105c5",
"view_tag": "67"
}
}
}
],
"extra": [ 1, 70, 84, 75, 61, 197, 61, 252, 168, 21, 100, 136, 241, 8, 12, 176, 190, 159, 66, 116, 237, 227, 40, 213, 243, 226, 188, 220, 72, 153, 160, 197, 94, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}