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: b091a48607a52f892b1dec3852d7bf57c2785fd7888658081a3eb3fbf445bfe8
Tx prefix hash: ed7e242030ba38f2d82bfe096200d3279b98ec0fd4836c51bd1216f91e79eea4
Tx public key: c5dd49c553c62d09097934f5306a75f97823e45bae63a6a6c2ecdf6a5b0ff1c0
| Timestamp: 1781019577 | Timestamp [UTC]: 2026-06-09 15:39:37 | Age [y:d:h:m:s]: 00:007:16:49:35 |
| Block: 8675 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 70 | RingCT/type: yes/0 |
| Extra: 01c5dd49c553c62d09097934f5306a75f97823e45bae63a6a6c2ecdf6a5b0ff1c0020900000001e49593ff00 | ||
1 output(s) for total of 34.613690460669 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9d715b5f89e3c637adf72a4c1c85e107f056dcfb8896a37ee58e0da276614cd5 | 34.613690460669 | 10725 of 0 | <fa> |
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": 8735,
"vin": [ {
"gen": {
"height": 8675
}
}
],
"vout": [ {
"amount": 34613690460669,
"target": {
"tagged_key": {
"key": "9d715b5f89e3c637adf72a4c1c85e107f056dcfb8896a37ee58e0da276614cd5",
"view_tag": "fa"
}
}
}
],
"extra": [ 1, 197, 221, 73, 197, 83, 198, 45, 9, 9, 121, 52, 245, 48, 106, 117, 249, 120, 35, 228, 91, 174, 99, 166, 166, 194, 236, 223, 106, 91, 15, 241, 192, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}