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: 3dc2ba99b15e408f329cbb6c15dbf0638f5f2f244b5b55f9f299e60f4605cdf9
Tx prefix hash: bafb0f32c36deebb2ee111c3c38e96bb1bd449ee790c23da0c0fec6d3a6c8f63
Tx public key: 84918513dd992fec2ae1265335d0d542cf9dc975f67c63cac0b3f5e99a65ed67
| Timestamp: 1780807585 | Timestamp [UTC]: 2026-06-07 04:46:25 | Age [y:d:h:m:s]: 00:001:20:00:22 |
| Block: 6970 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 916 | RingCT/type: yes/0 |
| Extra: 0184918513dd992fec2ae1265335d0d542cf9dc975f67c63cac0b3f5e99a65ed67020900000004e49593ff00 | ||
1 output(s) for total of 34.719784534648 HMNY
| stealth address | amount | amount idx | tag |
| 00: b3a506f1fe1dad732e8cbe50894360126dc3168d8c0ab4248f03670d13b768ab | 34.719784534648 | 8596 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": 7030,
"vin": [ {
"gen": {
"height": 6970
}
}
],
"vout": [ {
"amount": 34719784534648,
"target": {
"tagged_key": {
"key": "b3a506f1fe1dad732e8cbe50894360126dc3168d8c0ab4248f03670d13b768ab",
"view_tag": "43"
}
}
}
],
"extra": [ 1, 132, 145, 133, 19, 221, 153, 47, 236, 42, 225, 38, 83, 53, 208, 213, 66, 207, 157, 201, 117, 246, 124, 99, 202, 192, 179, 245, 233, 154, 101, 237, 103, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}