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: 32137f52a7002f00334ed7a233683c0984b8c2832ed43d4f55df8b7946de08b1
Tx prefix hash: 10218eda7a0a2a11674b565af6607b299dcd0fea8cadade918efec8cbe683da4
Tx public key: 177c83f38a137a2084e953546150d6477a6e991e3c63b76aff221b8aded27709
| Timestamp: 1780714916 | Timestamp [UTC]: 2026-06-06 03:01:56 | Age [y:d:h:m:s]: 00:002:21:44:51 |
| Block: 6188 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1698 | RingCT/type: yes/0 |
| Extra: 01177c83f38a137a2084e953546150d6477a6e991e3c63b76aff221b8aded27709020900000002e49593ff00 | ||
1 output(s) for total of 34.771609401714 HMNY
| stealth address | amount | amount idx | tag |
| 00: d561df0f95969f2a20ab06c72cb591525bb8f563d6066227a2c48bddd799542f | 34.771609401714 | 7665 of 0 | <85> |
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": 6248,
"vin": [ {
"gen": {
"height": 6188
}
}
],
"vout": [ {
"amount": 34771609401714,
"target": {
"tagged_key": {
"key": "d561df0f95969f2a20ab06c72cb591525bb8f563d6066227a2c48bddd799542f",
"view_tag": "85"
}
}
}
],
"extra": [ 1, 23, 124, 131, 243, 138, 19, 122, 32, 132, 233, 83, 84, 97, 80, 214, 71, 122, 110, 153, 30, 60, 99, 183, 106, 255, 34, 27, 138, 222, 210, 119, 9, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}