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: f6136b0da4ea6a82a2be127d5aaeca7a0094cc42d7474ce45f2b4bfc79a161cc
Tx prefix hash: 4a19cda7d8a11cff1e1a47c0e6484a09c16b6432b2051667332ff8b34815d6d6
Tx public key: bf060ce2c21b6932ec2be8ddba94a6cd6786b13aec090dc65b747d36892d20e8
| Timestamp: 1779962604 | Timestamp [UTC]: 2026-05-28 10:03:24 | Age [y:d:h:m:s]: 00:016:00:58:52 |
| Block: 3777 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4968 | RingCT/type: yes/0 |
| Extra: 01bf060ce2c21b6932ec2be8ddba94a6cd6786b13aec090dc65b747d36892d20e802090000000126697be300 | ||
1 output(s) for total of 34.931879115044 HMNY
| stealth address | amount | amount idx | tag |
| 00: bcc50a90800f86059018b1cfe79a67a607602c93dcbbc26e98b543f43e156067 | 34.931879115044 | 4584 of 0 | <88> |
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": 3837,
"vin": [ {
"gen": {
"height": 3777
}
}
],
"vout": [ {
"amount": 34931879115044,
"target": {
"tagged_key": {
"key": "bcc50a90800f86059018b1cfe79a67a607602c93dcbbc26e98b543f43e156067",
"view_tag": "88"
}
}
}
],
"extra": [ 1, 191, 6, 12, 226, 194, 27, 105, 50, 236, 43, 232, 221, 186, 148, 166, 205, 103, 134, 177, 58, 236, 9, 13, 198, 91, 116, 125, 54, 137, 45, 32, 232, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}