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: 8bc8701f40c6607fff5418fcd38a0c124febdb3dccaedfec92326d7e33fd53ba
Tx prefix hash: 9426738d60fe1d33ade784b6635667d9126cdbb51ded67407ecbcb8dba852b5e
Tx public key: 4188188de6e5b439aef9b4e418474e85aa93bb4b39b662223002135a71f52a4b
| Timestamp: 1780864735 | Timestamp [UTC]: 2026-06-07 20:38:55 | Age [y:d:h:m:s]: 00:005:14:23:21 |
| Block: 7647 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1098 | RingCT/type: yes/0 |
| Extra: 014188188de6e5b439aef9b4e418474e85aa93bb4b39b662223002135a71f52a4b020900000002e49593ff00 | ||
1 output(s) for total of 34.674980634601 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9eefb6e439de645d5f328f73ca9456d17b34fa53f371313f27feb0e7bcf174ee | 34.674980634601 | 9455 of 0 | <a8> |
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": 7707,
"vin": [ {
"gen": {
"height": 7647
}
}
],
"vout": [ {
"amount": 34674980634601,
"target": {
"tagged_key": {
"key": "9eefb6e439de645d5f328f73ca9456d17b34fa53f371313f27feb0e7bcf174ee",
"view_tag": "a8"
}
}
}
],
"extra": [ 1, 65, 136, 24, 141, 230, 229, 180, 57, 174, 249, 180, 228, 24, 71, 78, 133, 170, 147, 187, 75, 57, 182, 98, 34, 48, 2, 19, 90, 113, 245, 42, 75, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}