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: 1ff18a1f7ea8974c76a6a78a3c17f2fa5d4f989e2d56f05c3fa8feae6601c8f4
Tx prefix hash: 2a0e75a21be785c7884c22902bf6cf6a2533b348f54a42e42a2060d26a5e088f
Tx public key: b547cb4fddc865621d33e7e7726ba9c9713f21cc334872a42c38798369d79ba2
| Timestamp: 1779905051 | Timestamp [UTC]: 2026-05-27 18:04:11 | Age [y:d:h:m:s]: 00:020:14:18:08 |
| Block: 3185 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5560 | RingCT/type: yes/0 |
| Extra: 01b547cb4fddc865621d33e7e7726ba9c9713f21cc334872a42c38798369d79ba202090000000226697be300 | ||
1 output(s) for total of 34.971344774769 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4f7eb1ad5bc5db9485e3723614aac993b9352f7f72aa7c8c27131d47cfb9aa48 | 34.971344774769 | 3813 of 0 | <b0> |
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": 3245,
"vin": [ {
"gen": {
"height": 3185
}
}
],
"vout": [ {
"amount": 34971344774769,
"target": {
"tagged_key": {
"key": "4f7eb1ad5bc5db9485e3723614aac993b9352f7f72aa7c8c27131d47cfb9aa48",
"view_tag": "b0"
}
}
}
],
"extra": [ 1, 181, 71, 203, 79, 221, 200, 101, 98, 29, 51, 231, 231, 114, 107, 169, 201, 113, 63, 33, 204, 51, 72, 114, 164, 44, 56, 121, 131, 105, 215, 155, 162, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}