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: 48444b1f8a5ac45ade964cb3154d31fe0af53947b8a306d1a1f902dfa3b625a1
Tx prefix hash: 78452c9a89799e2c0ad60ae2f2a3fd3abdc9d23b024403a4d07438d462110fee
Tx public key: f9f908b931c990d5242e6216bace09f89f80460819a15babb3a6e0df2be784d9
| Timestamp: 1780866057 | Timestamp [UTC]: 2026-06-07 21:00:57 | Age [y:d:h:m:s]: 00:001:04:35:00 |
| Block: 7665 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 221 | RingCT/type: yes/0 |
| Extra: 01f9f908b931c990d5242e6216bace09f89f80460819a15babb3a6e0df2be784d9020900000003e49593ff00 | ||
1 output(s) for total of 34.679611382917 HMNY
| stealth address | amount | amount idx | tag |
| 00: c5bd44749508533f8da767b21962a1af451be37b786c83ec2cad07602c5aa7f3 | 34.679611382917 | 9477 of 0 | <e2> |
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": 7725,
"vin": [ {
"gen": {
"height": 7665
}
}
],
"vout": [ {
"amount": 34679611382917,
"target": {
"tagged_key": {
"key": "c5bd44749508533f8da767b21962a1af451be37b786c83ec2cad07602c5aa7f3",
"view_tag": "e2"
}
}
}
],
"extra": [ 1, 249, 249, 8, 185, 49, 201, 144, 213, 36, 46, 98, 22, 186, 206, 9, 248, 159, 128, 70, 8, 25, 161, 91, 171, 179, 166, 224, 223, 43, 231, 132, 217, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}