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: c56291e81d0f9b9092e2d3cc93cceee2e3fc1eb0bd95cc7f27c919d7a3e10bfa
Tx prefix hash: 74824355a1e6dcef3c584895f083bc28d32d7ea99338d13bbb6650f534c8c0fc
Tx public key: 99ec2e6e3b2da929f93ffd2db08551c37dd9f2a844117eaa15b1b0f50a4cfc4c
| Timestamp: 1780727840 | Timestamp [UTC]: 2026-06-06 06:37:20 | Age [y:d:h:m:s]: 00:002:18:09:27 |
| Block: 6291 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1595 | RingCT/type: yes/0 |
| Extra: 0199ec2e6e3b2da929f93ffd2db08551c37dd9f2a844117eaa15b1b0f50a4cfc4c020900000005e49593ff00 | ||
1 output(s) for total of 34.764778943257 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8aea88940d8d1634abbe996cfd9618df423e54fce45c17ece18c9e60ec02711e | 34.764778943257 | 7774 of 0 | <be> |
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": 6351,
"vin": [ {
"gen": {
"height": 6291
}
}
],
"vout": [ {
"amount": 34764778943257,
"target": {
"tagged_key": {
"key": "8aea88940d8d1634abbe996cfd9618df423e54fce45c17ece18c9e60ec02711e",
"view_tag": "be"
}
}
}
],
"extra": [ 1, 153, 236, 46, 110, 59, 45, 169, 41, 249, 63, 253, 45, 176, 133, 81, 195, 125, 217, 242, 168, 68, 17, 126, 170, 21, 177, 176, 245, 10, 76, 252, 76, 2, 9, 0, 0, 0, 5, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}