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: 7f7fe49e5ab7b5a9a9f9081811fdd23349d35dd532a1902698f392f458a6310f
Tx prefix hash: 8ae3704cc0ae49045863bbd3ceb088bec968ad26b36d34dfccf9418c2e48290a
Tx public key: 826b136ddd3f6e5c1a2c3ff5500ecb61e070762ab1ab6d70806625295ed907d7
| Timestamp: 1781000424 | Timestamp [UTC]: 2026-06-09 10:20:24 | Age [y:d:h:m:s]: 00:005:21:59:11 |
| Block: 8433 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 312 | RingCT/type: yes/0 |
| Extra: 01826b136ddd3f6e5c1a2c3ff5500ecb61e070762ab1ab6d70806625295ed907d7020900000001e49593ff00 | ||
1 output(s) for total of 34.623035632494 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2833d9f273583fb8e1ee310e0b89cc98118f946384067ad91cf901f4dbd694a0 | 34.623035632494 | 10423 of 0 | <a5> |
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": 8493,
"vin": [ {
"gen": {
"height": 8433
}
}
],
"vout": [ {
"amount": 34623035632494,
"target": {
"tagged_key": {
"key": "2833d9f273583fb8e1ee310e0b89cc98118f946384067ad91cf901f4dbd694a0",
"view_tag": "a5"
}
}
}
],
"extra": [ 1, 130, 107, 19, 109, 221, 63, 110, 92, 26, 44, 63, 245, 80, 14, 203, 97, 224, 112, 118, 42, 177, 171, 109, 112, 128, 102, 37, 41, 94, 217, 7, 215, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}