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: 337a78ab0a4f8252a933b7f3ea983050e55fe0784fa4f0509c6d4ce1920806e9
Tx prefix hash: fa234f24553096d91b63d20556d391ce43718267278acd2526cfa3e126859503
Tx public key: 6ef8f56a67df4b5ee46d7dc4e3c1087de07b5531150c90db68cf13f9d915a4d9
| Timestamp: 1779443485 | Timestamp [UTC]: 2026-05-22 09:51:25 | Age [y:d:h:m:s]: 00:017:16:49:11 |
| Block: 237 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7660 | RingCT/type: yes/0 |
| Extra: 016ef8f56a67df4b5ee46d7dc4e3c1087de07b5531150c90db68cf13f9d915a4d90209000000034438f87f00 | ||
1 output(s) for total of 35.168537945953 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3b48d306139883c7ab2d788e468e1b160bf6bab33c64b9bbfee5a14ed9b2d960 | 35.168537945953 | 233 of 0 | <e6> |
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": 297,
"vin": [ {
"gen": {
"height": 237
}
}
],
"vout": [ {
"amount": 35168537945953,
"target": {
"tagged_key": {
"key": "3b48d306139883c7ab2d788e468e1b160bf6bab33c64b9bbfee5a14ed9b2d960",
"view_tag": "e6"
}
}
}
],
"extra": [ 1, 110, 248, 245, 106, 103, 223, 75, 94, 228, 109, 125, 196, 227, 193, 8, 125, 224, 123, 85, 49, 21, 12, 144, 219, 104, 207, 19, 249, 217, 21, 164, 217, 2, 9, 0, 0, 0, 3, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}