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: a86ebee0ff881749b655c1c4bb6049f42e26fa3c0f3f618ca04ee09896f277e2
Tx prefix hash: 3ec843e10dfc7e15a8b739b9d318aff551ee28e72c1260e8e71def1d679402e1
Tx public key: 3fdbdc5fc0133305476abcd2c75d26057a417e60fb10cc38d0b24e185c4ab4f8
| Timestamp: 1780737705 | Timestamp [UTC]: 2026-06-06 09:21:45 | Age [y:d:h:m:s]: 00:007:01:40:31 |
| Block: 6382 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2363 | RingCT/type: yes/0 |
| Extra: 013fdbdc5fc0133305476abcd2c75d26057a417e60fb10cc38d0b24e185c4ab4f8020900000001e49593ff00 | ||
1 output(s) for total of 34.758745382760 HMNY
| stealth address | amount | amount idx | tag |
| 00: ff8bf5af3526fa4512991b4ca703b97cace3221177fd1596412524865226198b | 34.758745382760 | 7871 of 0 | <03> |
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": 6442,
"vin": [ {
"gen": {
"height": 6382
}
}
],
"vout": [ {
"amount": 34758745382760,
"target": {
"tagged_key": {
"key": "ff8bf5af3526fa4512991b4ca703b97cace3221177fd1596412524865226198b",
"view_tag": "03"
}
}
}
],
"extra": [ 1, 63, 219, 220, 95, 192, 19, 51, 5, 71, 106, 188, 210, 199, 93, 38, 5, 122, 65, 126, 96, 251, 16, 204, 56, 208, 178, 78, 24, 92, 74, 180, 248, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}