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: 069a4f50a0a0f5fc04ddb39f2f7a957c7bb03f0bdf8eea402bd07872f0545bd7
Tx prefix hash: a81a67d1f1051e1ef21689ea9175b8155e6a5f06b7dd8d734aacc797b51025e7
Tx public key: 7f4cc4d24eb3a86f1ed5ba1fcc7411a8be63463f576c0756840862569f14408f
| Timestamp: 1779461109 | Timestamp [UTC]: 2026-05-22 14:45:09 | Age [y:d:h:m:s]: 00:017:10:50:48 |
| Block: 438 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7448 | RingCT/type: yes/0 |
| Extra: 017f4cc4d24eb3a86f1ed5ba1fcc7411a8be63463f576c0756840862569f14408f02090000000393369e7d00 | ||
1 output(s) for total of 35.155057706053 HMNY
| stealth address | amount | amount idx | tag |
| 00: e64e13e15bea2a0d6ee40ee0a9de8ae3b3c9f9dedf261d8c337690a0c5ae9e3b | 35.155057706053 | 442 of 0 | <1c> |
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": 498,
"vin": [ {
"gen": {
"height": 438
}
}
],
"vout": [ {
"amount": 35155057706053,
"target": {
"tagged_key": {
"key": "e64e13e15bea2a0d6ee40ee0a9de8ae3b3c9f9dedf261d8c337690a0c5ae9e3b",
"view_tag": "1c"
}
}
}
],
"extra": [ 1, 127, 76, 196, 210, 78, 179, 168, 111, 30, 213, 186, 31, 204, 116, 17, 168, 190, 99, 70, 63, 87, 108, 7, 86, 132, 8, 98, 86, 159, 20, 64, 143, 2, 9, 0, 0, 0, 3, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}