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: b156d464ff6a109bbdf7c8db5d6326f38be03439fe133f9a5835cd5f42d5a1ac
Tx prefix hash: 3880ce0f03a2237e588dd547e37e8812afca42a2bb763f452fa2a5e3a659e516
Tx public key: 5e5cf104534754f68fd77bfc1c822bd5c971b53e46094341305e8cc295d56f5a
| Timestamp: 1781022140 | Timestamp [UTC]: 2026-06-09 16:22:20 | Age [y:d:h:m:s]: 00:006:05:15:04 |
| Block: 8704 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 41 | RingCT/type: yes/0 |
| Extra: 015e5cf104534754f68fd77bfc1c822bd5c971b53e46094341305e8cc295d56f5a020900000001e49593ff00 | ||
1 output(s) for total of 34.605143887762 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2b51b7792a67ec674d3864d52d9c2826c5814d0fef6fa3c43217689bcf4e63ab | 34.605143887762 | 10764 of 0 | <cd> |
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": 8764,
"vin": [ {
"gen": {
"height": 8704
}
}
],
"vout": [ {
"amount": 34605143887762,
"target": {
"tagged_key": {
"key": "2b51b7792a67ec674d3864d52d9c2826c5814d0fef6fa3c43217689bcf4e63ab",
"view_tag": "cd"
}
}
}
],
"extra": [ 1, 94, 92, 241, 4, 83, 71, 84, 246, 143, 215, 123, 252, 28, 130, 43, 213, 201, 113, 181, 62, 70, 9, 67, 65, 48, 94, 140, 194, 149, 213, 111, 90, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}