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: 71c3da8c9537016d3ccdf68bb5504614a2ac3274c399a79d9f49e94b1f74a9d8
Tx prefix hash: c815cf680825281c19bb91d4d6ad5af3d010458cfe61225428e1718b930b606d
Tx public key: 516dd13addce9df68e6418c7bdeeea7b57cce2f9c40daf6cf44718e1f2e91a9f
| Timestamp: 1779711623 | Timestamp [UTC]: 2026-05-25 12:20:23 | Age [y:d:h:m:s]: 00:014:12:26:24 |
| Block: 1584 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6302 | RingCT/type: yes/0 |
| Extra: 01516dd13addce9df68e6418c7bdeeea7b57cce2f9c40daf6cf44718e1f2e91a9f020900000008ba6d17be00 | ||
1 output(s) for total of 35.078298871834 HMNY
| stealth address | amount | amount idx | tag |
| 00: d29aee7889c64fb4d337a49cb12fc4690145742f2e3ef009449672c0f926390d | 35.078298871834 | 1742 of 0 | <32> |
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": 1644,
"vin": [ {
"gen": {
"height": 1584
}
}
],
"vout": [ {
"amount": 35078298871834,
"target": {
"tagged_key": {
"key": "d29aee7889c64fb4d337a49cb12fc4690145742f2e3ef009449672c0f926390d",
"view_tag": "32"
}
}
}
],
"extra": [ 1, 81, 109, 209, 58, 221, 206, 157, 246, 142, 100, 24, 199, 189, 238, 234, 123, 87, 204, 226, 249, 196, 13, 175, 108, 244, 71, 24, 225, 242, 233, 26, 159, 2, 9, 0, 0, 0, 8, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}