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: b3fe42dbd684adcecce97bfd06a8b6ec681b2ebaa0db2e51169acaa3ddcb4e40
Tx prefix hash: e93b14b8e20dd1e69d45efb319bd132816d6c7c1c934442ff8d8b4a5842e5ffb
Tx public key: 05f6956648b4a315bbf8ab7fb74b3c0e7930411ac1f8d809e90a95a5c3bb01ed
| Timestamp: 1780803455 | Timestamp [UTC]: 2026-06-07 03:37:35 | Age [y:d:h:m:s]: 00:006:07:24:41 |
| Block: 6887 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1858 | RingCT/type: yes/0 |
| Extra: 0105f6956648b4a315bbf8ab7fb74b3c0e7930411ac1f8d809e90a95a5c3bb01ed020900000002e49593ff00 | ||
1 output(s) for total of 34.725281461874 HMNY
| stealth address | amount | amount idx | tag |
| 00: 69ea285684ab3042414a9498a34056b20ccf47d60de737a9b929056f9844e50f | 34.725281461874 | 8499 of 0 | <6f> |
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": 6947,
"vin": [ {
"gen": {
"height": 6887
}
}
],
"vout": [ {
"amount": 34725281461874,
"target": {
"tagged_key": {
"key": "69ea285684ab3042414a9498a34056b20ccf47d60de737a9b929056f9844e50f",
"view_tag": "6f"
}
}
}
],
"extra": [ 1, 5, 246, 149, 102, 72, 180, 163, 21, 187, 248, 171, 127, 183, 75, 60, 14, 121, 48, 65, 26, 193, 248, 216, 9, 233, 10, 149, 165, 195, 187, 1, 237, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}