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: 161d769cb707c05aa3ea6f70ec9498b2ed97922e9ddd98fb71a263279f8d3521
Tx prefix hash: 4def946d8261ac06e4f522c73ecf5f5efdc89e5fc42d760301e713dc5ed63c72
Tx public key: d143959710c5652e5da76a3bdb349e82facad7bd7c33e55769e6010cb1703922
| Timestamp: 1780987505 | Timestamp [UTC]: 2026-06-09 06:45:05 | Age [y:d:h:m:s]: 00:000:08:03:50 |
| Block: 8172 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 481 | RingCT/type: yes/0 |
| Extra: 01d143959710c5652e5da76a3bdb349e82facad7bd7c33e55769e6010cb1703922020900000003e49593ff00 | ||
1 output(s) for total of 34.640275909956 HMNY
| stealth address | amount | amount idx | tag |
| 00: ec3c278f4bd5b822fb0dd925ad8ccf213cc3136939cae7b7c50f020dbb00ebf0 | 34.640275909956 | 10118 of 0 | <1e> |
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": 8232,
"vin": [ {
"gen": {
"height": 8172
}
}
],
"vout": [ {
"amount": 34640275909956,
"target": {
"tagged_key": {
"key": "ec3c278f4bd5b822fb0dd925ad8ccf213cc3136939cae7b7c50f020dbb00ebf0",
"view_tag": "1e"
}
}
}
],
"extra": [ 1, 209, 67, 149, 151, 16, 197, 101, 46, 93, 167, 106, 59, 219, 52, 158, 130, 250, 202, 215, 189, 124, 51, 229, 87, 105, 230, 1, 12, 177, 112, 57, 34, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}