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: 4be6ff647c6f8536f0b83c8ec3e007be66c6bf28de9e0c2e10f777c9c25ce37a
Tx prefix hash: ffffbb376d9ccab2b51b24c4aa7d11da015e94be76f7d0aea808daf3d4ae6c04
Tx public key: 95f17e8f5dd05af5ae02993f10fc1084c7edfa938a1f48d5b74cb253b2f8210f
| Timestamp: 1780393112 | Timestamp [UTC]: 2026-06-02 09:38:32 | Age [y:d:h:m:s]: 00:006:15:57:25 |
| Block: 5224 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2662 | RingCT/type: yes/0 |
| Extra: 0195f17e8f5dd05af5ae02993f10fc1084c7edfa938a1f48d5b74cb253b2f8210f02090000000526697be300 | ||
1 output(s) for total of 34.839022280771 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0d6d03e621ed81d2c998b8bcbfa39a3e215988c9227808adb7157786a0a28161 | 34.839022280771 | 6611 of 0 | <09> |
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": 5284,
"vin": [ {
"gen": {
"height": 5224
}
}
],
"vout": [ {
"amount": 34839022280771,
"target": {
"tagged_key": {
"key": "0d6d03e621ed81d2c998b8bcbfa39a3e215988c9227808adb7157786a0a28161",
"view_tag": "09"
}
}
}
],
"extra": [ 1, 149, 241, 126, 143, 93, 208, 90, 245, 174, 2, 153, 63, 16, 252, 16, 132, 199, 237, 250, 147, 138, 31, 72, 213, 183, 76, 178, 83, 178, 248, 33, 15, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}