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: ae7e0ac591fcc4780046cd22ca3ee1e5dc23563ea9e8a0440bd1072bc1165937
Tx prefix hash: c81491e08a3f13aa864f90daf55303fd0376dd14404d9b6bce0936ff1bb004f5
Tx public key: a707957fd8917698cd1795c7b5be123d32b9dd02ac8fc9c2699e989c6a6342d0
| Timestamp: 1779461131 | Timestamp [UTC]: 2026-05-22 14:45:31 | Age [y:d:h:m:s]: 00:025:17:19:50 |
| Block: 439 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 8306 | RingCT/type: yes/0 |
| Extra: 01a707957fd8917698cd1795c7b5be123d32b9dd02ac8fc9c2699e989c6a6342d002090000000293369e7d00 | ||
1 output(s) for total of 35.154990653102 HMNY
| stealth address | amount | amount idx | tag |
| 00: 87c219609f4981364dc255d59ceb0a0a59338fb4318e6f4ea16c157ba5bd625f | 35.154990653102 | 443 of 0 | <43> |
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": 499,
"vin": [ {
"gen": {
"height": 439
}
}
],
"vout": [ {
"amount": 35154990653102,
"target": {
"tagged_key": {
"key": "87c219609f4981364dc255d59ceb0a0a59338fb4318e6f4ea16c157ba5bd625f",
"view_tag": "43"
}
}
}
],
"extra": [ 1, 167, 7, 149, 127, 216, 145, 118, 152, 205, 23, 149, 199, 181, 190, 18, 61, 50, 185, 221, 2, 172, 143, 201, 194, 105, 158, 152, 156, 106, 99, 66, 208, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}