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: 2f51e7d6cfbdf1ef7c3097b2b332d416c35cfb4ae59feb9b1f6a243fa1fcd849
Tx prefix hash: 17571bd4669cc0547ea1e94c37841fed38bc5f51121b994f0070437daf26b559
Tx public key: 5547b34771aaa06e9c7470a2e2249c861289fc42f41c9ca15acc6704788986ed
| Timestamp: 1780839609 | Timestamp [UTC]: 2026-06-07 13:40:09 | Age [y:d:h:m:s]: 00:005:21:40:56 |
| Block: 7449 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1296 | RingCT/type: yes/0 |
| Extra: 015547b34771aaa06e9c7470a2e2249c861289fc42f41c9ca15acc6704788986ed020900000002e49593ff00 | ||
1 output(s) for total of 34.692299900964 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2a42d104696192526ddc69639f308f04c7c1c78dd6e9347ffdbedf35eb6de76f | 34.692299900964 | 9173 of 0 | <06> |
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": 7509,
"vin": [ {
"gen": {
"height": 7449
}
}
],
"vout": [ {
"amount": 34692299900964,
"target": {
"tagged_key": {
"key": "2a42d104696192526ddc69639f308f04c7c1c78dd6e9347ffdbedf35eb6de76f",
"view_tag": "06"
}
}
}
],
"extra": [ 1, 85, 71, 179, 71, 113, 170, 160, 110, 156, 116, 112, 162, 226, 36, 156, 134, 18, 137, 252, 66, 244, 28, 156, 161, 90, 204, 103, 4, 120, 137, 134, 237, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}