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: f35fb27bc2b4c5beb9fcb290e6cb1a5f7d2c5819df81635b6d051f696ebb1735
Tx prefix hash: fcb58c481bffd791800f0532de3d94b914ebfe44a050409f2f3b4956e20fab8a
Tx public key: 57ad223f47b696350a6df920fbaa6b5c88fe6e34a891adae2e6cdbe1ea89dfbf
| Timestamp: 1780823373 | Timestamp [UTC]: 2026-06-07 09:09:33 | Age [y:d:h:m:s]: 00:010:00:05:33 |
| Block: 7216 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1529 | RingCT/type: yes/0 |
| Extra: 0157ad223f47b696350a6df920fbaa6b5c88fe6e34a891adae2e6cdbe1ea89dfbf020900000001e49593ff00 | ||
1 output(s) for total of 34.711719947948 HMNY
| stealth address | amount | amount idx | tag |
| 00: 99b39a2e5d44d7aa133cc007f4a4e68e2a825037df0e228f8dcac3692e0821a2 | 34.711719947948 | 8886 of 0 | <b9> |
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": 7276,
"vin": [ {
"gen": {
"height": 7216
}
}
],
"vout": [ {
"amount": 34711719947948,
"target": {
"tagged_key": {
"key": "99b39a2e5d44d7aa133cc007f4a4e68e2a825037df0e228f8dcac3692e0821a2",
"view_tag": "b9"
}
}
}
],
"extra": [ 1, 87, 173, 34, 63, 71, 182, 150, 53, 10, 109, 249, 32, 251, 170, 107, 92, 136, 254, 110, 52, 168, 145, 173, 174, 46, 108, 219, 225, 234, 137, 223, 191, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}