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: 70a4f7bef0cd95ef94f14ac71f4af16c6a3c6113d1dd8cfea83c40bac842aadc
Tx prefix hash: 88ddc227e173ba5950606989231c3c5d6fc38435121f0532be4a7a6b3c58673e
Tx public key: 87852609550b4dacefdbf5d31d4a31794de07be3c7db3a6477d441c96a1f749a
| Timestamp: 1779445238 | Timestamp [UTC]: 2026-05-22 10:20:38 | Age [y:d:h:m:s]: 00:017:17:18:12 |
| Block: 268 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7679 | RingCT/type: yes/0 |
| Extra: 0187852609550b4dacefdbf5d31d4a31794de07be3c7db3a6477d441c96a1f749a0209000000014438f87f00 | ||
1 output(s) for total of 35.166458566899 HMNY
| stealth address | amount | amount idx | tag |
| 00: 35faca382db1f5a1c67b7c2da2bb39615000fa92ac2aca109fbbc30151371546 | 35.166458566899 | 264 of 0 | <80> |
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": 328,
"vin": [ {
"gen": {
"height": 268
}
}
],
"vout": [ {
"amount": 35166458566899,
"target": {
"tagged_key": {
"key": "35faca382db1f5a1c67b7c2da2bb39615000fa92ac2aca109fbbc30151371546",
"view_tag": "80"
}
}
}
],
"extra": [ 1, 135, 133, 38, 9, 85, 11, 77, 172, 239, 219, 245, 211, 29, 74, 49, 121, 77, 224, 123, 227, 199, 219, 58, 100, 119, 212, 65, 201, 106, 31, 116, 154, 2, 9, 0, 0, 0, 1, 68, 56, 248, 127, 0
],
"rct_signatures": {
"type": 0
}
}