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: 2b82c27fef90e6dd17339666325827583d54ed1f83d7ed1eb9d7a37ddb9ae367
Tx prefix hash: 17bd1193ecd4d5ae7dfd8343b49a87ed74b49c2ca7484abe95799497dfe8cc14
Tx public key: 9789a81e792ab011cc3436b44e23fe99c0dcc85df9ed50ef5ab844a8a07efaa2
| Timestamp: 1779730704 | Timestamp [UTC]: 2026-05-25 17:38:24 | Age [y:d:h:m:s]: 00:014:07:57:33 |
| Block: 1879 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6007 | RingCT/type: yes/0 |
| Extra: 019789a81e792ab011cc3436b44e23fe99c0dcc85df9ed50ef5ab844a8a07efaa2020900000003ba6d17be00 | ||
1 output(s) for total of 35.058566973897 HMNY
| stealth address | amount | amount idx | tag |
| 00: b91c8879b98564fe28c01b7fed5dc73ed1d1f39db7bb4d88eed0b4bcaeb380d1 | 35.058566973897 | 2094 of 0 | <a1> |
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": 1939,
"vin": [ {
"gen": {
"height": 1879
}
}
],
"vout": [ {
"amount": 35058566973897,
"target": {
"tagged_key": {
"key": "b91c8879b98564fe28c01b7fed5dc73ed1d1f39db7bb4d88eed0b4bcaeb380d1",
"view_tag": "a1"
}
}
}
],
"extra": [ 1, 151, 137, 168, 30, 121, 42, 176, 17, 204, 52, 54, 180, 78, 35, 254, 153, 192, 220, 200, 93, 249, 237, 80, 239, 90, 184, 68, 168, 160, 126, 250, 162, 2, 9, 0, 0, 0, 3, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}