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: f9739f4c89c0aae802a36e5c5974dab2ed3e382d9f1378cb16baf440f6adad60
Tx prefix hash: 61c17370941a79aba8090e1840b17b0f59685181a0e39d21a65aa3121de87543
Tx public key: 244401291adeee01f727d9c68a907689bfb5fa0d3aeea577a72f921aa5045e1b
| Timestamp: 1780855349 | Timestamp [UTC]: 2026-06-07 18:02:29 | Age [y:d:h:m:s]: 00:001:03:09:38 |
| Block: 7567 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 319 | RingCT/type: yes/0 |
| Extra: 01244401291adeee01f727d9c68a907689bfb5fa0d3aeea577a72f921aa5045e1b020900000004e49593ff00 | ||
1 output(s) for total of 34.688483625491 HMNY
| stealth address | amount | amount idx | tag |
| 00: 221044f8ec39742ac8347dc688306f15c509f4629692059fe2c4f21f726d53e2 | 34.688483625491 | 9343 of 0 | <03> |
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": 7627,
"vin": [ {
"gen": {
"height": 7567
}
}
],
"vout": [ {
"amount": 34688483625491,
"target": {
"tagged_key": {
"key": "221044f8ec39742ac8347dc688306f15c509f4629692059fe2c4f21f726d53e2",
"view_tag": "03"
}
}
}
],
"extra": [ 1, 36, 68, 1, 41, 26, 222, 238, 1, 247, 39, 217, 198, 138, 144, 118, 137, 191, 181, 250, 13, 58, 238, 165, 119, 167, 47, 146, 26, 165, 4, 94, 27, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}