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: b83f96d785bf809d91008f53128e85e29af573a286fbdf4b30ca17198ebc2931
Tx prefix hash: b58170649c97b187cdfdf2f56d4259620e363d62c5354515105eee64ee9b4052
Tx public key: 6b6b26c5ee63d4c685403a29637d12941f0d37f75d1420b828c8feac734c521b
| Timestamp: 1779772755 | Timestamp [UTC]: 2026-05-26 05:19:15 | Age [y:d:h:m:s]: 00:022:03:09:57 |
| Block: 2035 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6710 | RingCT/type: yes/0 |
| Extra: 016b6b26c5ee63d4c685403a29637d12941f0d37f75d1420b828c8feac734c521b02090000000226697be300 | ||
1 output(s) for total of 35.048136965806 HMNY
| stealth address | amount | amount idx | tag |
| 00: 40aeba1100626636f27f978a4c44f479c9b97df8243692ce4df94cee40e354a6 | 35.048136965806 | 2327 of 0 | <30> |
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": 2095,
"vin": [ {
"gen": {
"height": 2035
}
}
],
"vout": [ {
"amount": 35048136965806,
"target": {
"tagged_key": {
"key": "40aeba1100626636f27f978a4c44f479c9b97df8243692ce4df94cee40e354a6",
"view_tag": "30"
}
}
}
],
"extra": [ 1, 107, 107, 38, 197, 238, 99, 212, 198, 133, 64, 58, 41, 99, 125, 18, 148, 31, 13, 55, 247, 93, 20, 32, 184, 40, 200, 254, 172, 115, 76, 82, 27, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}