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: 86e04277660fd71f7a3639c3a877fac8ca68ce881d0c99c0c4706f0d2116ca35
Tx prefix hash: f477c638c7c5cd2d2a16cf8dce4c5c52f8bd3038aa3d368c282c8eede11f104b
Tx public key: 6af92fa8f594f5f4aa4369dd15b06767cab78f40c98c178278d02a6e96172cba
| Timestamp: 1779451432 | Timestamp [UTC]: 2026-05-22 12:03:52 | Age [y:d:h:m:s]: 00:017:14:45:56 |
| Block: 331 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7589 | RingCT/type: yes/0 |
| Extra: 016af92fa8f594f5f4aa4369dd15b06767cab78f40c98c178278d02a6e96172cba0209000000024438f87f00 | ||
1 output(s) for total of 35.162233110856 HMNY
| stealth address | amount | amount idx | tag |
| 00: 977d96ed8f9774bed5769f9d36f582deaeea017955fb5136e25be44dac39bec9 | 35.162233110856 | 327 of 0 | <d5> |
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": 391,
"vin": [ {
"gen": {
"height": 331
}
}
],
"vout": [ {
"amount": 35162233110856,
"target": {
"tagged_key": {
"key": "977d96ed8f9774bed5769f9d36f582deaeea017955fb5136e25be44dac39bec9",
"view_tag": "d5"
}
}
}
],
"extra": [ 1, 106, 249, 47, 168, 245, 148, 245, 244, 170, 67, 105, 221, 21, 176, 103, 103, 202, 183, 143, 64, 201, 140, 23, 130, 120, 208, 42, 110, 150, 23, 44, 186, 2, 9, 0, 0, 0, 2, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}