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: 33bc4b6c34dad989d15f949d7d3926b47990c5d6fe0a4baef58db5de7d07d281
Tx prefix hash: e817cbeb021e1f6adac2bc765edd1b31d09355312f23ce5098ea67cadcc0de10
Tx public key: a102d03c0cf5a98ffb5700739db3aab81efbde8f42adacffc5df832ab2f4b66d
| Timestamp: 1779844615 | Timestamp [UTC]: 2026-05-27 01:16:55 | Age [y:d:h:m:s]: 00:013:02:21:55 |
| Block: 2436 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5510 | RingCT/type: yes/0 |
| Extra: 01a102d03c0cf5a98ffb5700739db3aab81efbde8f42adacffc5df832ab2f4b66d02090000000126697be300 | ||
1 output(s) for total of 35.021340733598 HMNY
| stealth address | amount | amount idx | tag |
| 00: 15da4cba2a41aee320aca2e825116d15256f034676403d7ce8f1c2cb73572287 | 35.021340733598 | 2862 of 0 | <7b> |
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": 2496,
"vin": [ {
"gen": {
"height": 2436
}
}
],
"vout": [ {
"amount": 35021340733598,
"target": {
"tagged_key": {
"key": "15da4cba2a41aee320aca2e825116d15256f034676403d7ce8f1c2cb73572287",
"view_tag": "7b"
}
}
}
],
"extra": [ 1, 161, 2, 208, 60, 12, 245, 169, 143, 251, 87, 0, 115, 157, 179, 170, 184, 30, 251, 222, 143, 66, 173, 172, 255, 197, 223, 131, 42, 178, 244, 182, 109, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}