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: 501ba968c3b0d7b3d1821d249a071684876f95a9539472bd81f5a230f05d1ddc
Tx prefix hash: f6df2a0ea9fa1beb981bcd5ac0c4d32c2ea02c4326192ab4d48a35e2484ab16b
Tx public key: 3b3d76979254263c736047800b2a1c20ed81c00e481995eea30a2a9387be43a6
| Timestamp: 1779630470 | Timestamp [UTC]: 2026-05-24 13:47:50 | Age [y:d:h:m:s]: 00:015:14:03:08 |
| Block: 871 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7081 | RingCT/type: yes/0 |
| Extra: 013b3d76979254263c736047800b2a1c20ed81c00e481995eea30a2a9387be43a6020900000001ba6d17be00 | ||
1 output(s) for total of 35.126035736494 HMNY
| stealth address | amount | amount idx | tag |
| 00: bf13c146b8af8418120c501bfbda29e30972bb35415aa87e43d5802c9e5f7309 | 35.126035736494 | 1003 of 0 | <a2> |
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": 931,
"vin": [ {
"gen": {
"height": 871
}
}
],
"vout": [ {
"amount": 35126035736494,
"target": {
"tagged_key": {
"key": "bf13c146b8af8418120c501bfbda29e30972bb35415aa87e43d5802c9e5f7309",
"view_tag": "a2"
}
}
}
],
"extra": [ 1, 59, 61, 118, 151, 146, 84, 38, 60, 115, 96, 71, 128, 11, 42, 28, 32, 237, 129, 192, 14, 72, 25, 149, 238, 163, 10, 42, 147, 135, 190, 67, 166, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}