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: f98cbb2ce06bb64c42c20ba43a4ca95af80bc0bc178f17f3c326380454e62d08
Tx prefix hash: d1bda535b60bd82bde176ecebfd63b0e85a69238aedc9be2d26b0f1ab66d6ab4
Tx public key: 7ea92132504ca5c10f4f537cff1f522442d76991490600be9c3ae7519b004ba3
| Timestamp: 1780777080 | Timestamp [UTC]: 2026-06-06 20:18:00 | Age [y:d:h:m:s]: 00:002:03:00:53 |
| Block: 6734 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1152 | RingCT/type: yes/0 |
| Extra: 017ea92132504ca5c10f4f537cff1f522442d76991490600be9c3ae7519b004ba3020900000003e49593ff00 | ||
1 output(s) for total of 34.735416632685 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2c6932456ecfd0ba84a3ba8432aca0747149f810b516bd20de08ccff6eec4e72 | 34.735416632685 | 8306 of 0 | <36> |
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": 6794,
"vin": [ {
"gen": {
"height": 6734
}
}
],
"vout": [ {
"amount": 34735416632685,
"target": {
"tagged_key": {
"key": "2c6932456ecfd0ba84a3ba8432aca0747149f810b516bd20de08ccff6eec4e72",
"view_tag": "36"
}
}
}
],
"extra": [ 1, 126, 169, 33, 50, 80, 76, 165, 193, 15, 79, 83, 124, 255, 31, 82, 36, 66, 215, 105, 145, 73, 6, 0, 190, 156, 58, 231, 81, 155, 0, 75, 163, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}