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: feb3707c58db7f9c583078deb4c090ee0d8bb58133826e4d51a7fa6079a195c5
Tx prefix hash: 2ca6546ec3917eebbcaf33c38bd1affd98d7552cb5a34d35c361acf8e438a96f
Tx public key: 1c91af402d20b01bd1b4ff05c6dfb2d23c2e88b7e830f70ed7d0e5b3d237fd4a
| Timestamp: 1779459412 | Timestamp [UTC]: 2026-05-22 14:16:52 | Age [y:d:h:m:s]: 00:017:10:29:55 |
| Block: 422 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7464 | RingCT/type: yes/0 |
| Extra: 011c91af402d20b01bd1b4ff05c6dfb2d23c2e88b7e830f70ed7d0e5b3d237fd4a02090000000293369e7d00 | ||
1 output(s) for total of 35.156130570667 HMNY
| stealth address | amount | amount idx | tag |
| 00: f6b6dab4731d27dd76c2318418a3aed9dd9050bb127c053b885e4baa4ba58991 | 35.156130570667 | 426 of 0 | <37> |
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": 482,
"vin": [ {
"gen": {
"height": 422
}
}
],
"vout": [ {
"amount": 35156130570667,
"target": {
"tagged_key": {
"key": "f6b6dab4731d27dd76c2318418a3aed9dd9050bb127c053b885e4baa4ba58991",
"view_tag": "37"
}
}
}
],
"extra": [ 1, 28, 145, 175, 64, 45, 32, 176, 27, 209, 180, 255, 5, 198, 223, 178, 210, 60, 46, 136, 183, 232, 48, 247, 14, 215, 208, 229, 179, 210, 55, 253, 74, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}