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: d2561b79b1b76d078600366f287b4535df10176783c672e632188a96f563f7d5
Tx prefix hash: 2b3d5e747bd276931ab2be9868db5a03af22813e7845be9f94c6b7023759939d
Tx public key: b3bc9636a6e55751c5b05c2290fca32c313203ac953dd8fb5f5397b73f3342ec
| Timestamp: 1780390198 | Timestamp [UTC]: 2026-06-02 08:49:58 | Age [y:d:h:m:s]: 00:006:16:45:59 |
| Block: 5202 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2684 | RingCT/type: yes/0 |
| Extra: 01b3bc9636a6e55751c5b05c2290fca32c313203ac953dd8fb5f5397b73f3342ec02090000000126697be300 | ||
1 output(s) for total of 34.837064072879 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4e6e5dabbea242d8fda50116a9cc33de2976f66f9ea3f6c6792a981bb073e76c | 34.837064072879 | 6583 of 0 | <d0> |
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": 5262,
"vin": [ {
"gen": {
"height": 5202
}
}
],
"vout": [ {
"amount": 34837064072879,
"target": {
"tagged_key": {
"key": "4e6e5dabbea242d8fda50116a9cc33de2976f66f9ea3f6c6792a981bb073e76c",
"view_tag": "d0"
}
}
}
],
"extra": [ 1, 179, 188, 150, 54, 166, 229, 87, 81, 197, 176, 92, 34, 144, 252, 163, 44, 49, 50, 3, 172, 149, 61, 216, 251, 95, 83, 151, 183, 63, 51, 66, 236, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}