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: 3e64e71dec8cdbc4fb423bf75ba4f8efa1c65e38c72d55d25913e86eeb8949b1
Tx prefix hash: 3c193a3764eb62e8ebaef03fff59fa9b15edee9d9754d168f64bf44566892c03
Tx public key: 417448c61de910558ce40c162e1eef82dfb12c181a626a8a413831d9f79105d2
| Timestamp: 1780079419 | Timestamp [UTC]: 2026-05-29 18:30:19 | Age [y:d:h:m:s]: 00:010:08:10:17 |
| Block: 4739 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3157 | RingCT/type: yes/0 |
| Extra: 01417448c61de910558ce40c162e1eef82dfb12c181a626a8a413831d9f79105d202090000000226697be300 | ||
1 output(s) for total of 34.867842385916 HMNY
| stealth address | amount | amount idx | tag |
| 00: adedd30260b5296d86a751e848799bd45885607e99058339c3bbfc53eda7582c | 34.867842385916 | 5958 of 0 | <b1> |
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": 4799,
"vin": [ {
"gen": {
"height": 4739
}
}
],
"vout": [ {
"amount": 34867842385916,
"target": {
"tagged_key": {
"key": "adedd30260b5296d86a751e848799bd45885607e99058339c3bbfc53eda7582c",
"view_tag": "b1"
}
}
}
],
"extra": [ 1, 65, 116, 72, 198, 29, 233, 16, 85, 140, 228, 12, 22, 46, 30, 239, 130, 223, 177, 44, 24, 26, 98, 106, 138, 65, 56, 49, 217, 247, 145, 5, 210, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}