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: 12a192ddf2da09c3793ae3d1c409d2601a3bacc6271e6694b469ab362ce744f5
Tx prefix hash: 76be4c67c5be1eae05e9c09dc34f7d4a1fe8eb0bdeb36363323cdf5c8585157e
Tx public key: 3e00296d8aac80bf236e68eb0236cb03838e35a45d7bff2c96ddf27f9b6188ed
| Timestamp: 1780323378 | Timestamp [UTC]: 2026-06-01 14:16:18 | Age [y:d:h:m:s]: 00:007:11:19:39 |
| Block: 5123 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2763 | RingCT/type: yes/0 |
| Extra: 013e00296d8aac80bf236e68eb0236cb03838e35a45d7bff2c96ddf27f9b6188ed02090000003e26697be300 | ||
1 output(s) for total of 34.842313741083 HMNY
| stealth address | amount | amount idx | tag |
| 00: 43a7dbd1a9394bf94aeb239ac2d13e44f0ff32c33ce207191303ecefa353b410 | 34.842313741083 | 6498 of 0 | <32> |
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": 5183,
"vin": [ {
"gen": {
"height": 5123
}
}
],
"vout": [ {
"amount": 34842313741083,
"target": {
"tagged_key": {
"key": "43a7dbd1a9394bf94aeb239ac2d13e44f0ff32c33ce207191303ecefa353b410",
"view_tag": "32"
}
}
}
],
"extra": [ 1, 62, 0, 41, 109, 138, 172, 128, 191, 35, 110, 104, 235, 2, 54, 203, 3, 131, 142, 53, 164, 93, 123, 255, 44, 150, 221, 242, 127, 155, 97, 136, 237, 2, 9, 0, 0, 0, 62, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}