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: e244fa158b3554a139904e496dfb1098a74ce3bad71708b045bfc54e534cc00e
Tx prefix hash: ecb38075203fe3b9841b3a3222d9dcb7c5f8696e243216b0c7ef34843360fd2a
Tx public key: f664b6cd6cad2b21a42d16a211d8f9beff77408c474ebcb818ddb33d84ddfc32
| Timestamp: 1780823348 | Timestamp [UTC]: 2026-06-07 09:09:08 | Age [y:d:h:m:s]: 00:001:15:37:39 |
| Block: 7215 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 671 | RingCT/type: yes/0 |
| Extra: 01f664b6cd6cad2b21a42d16a211d8f9beff77408c474ebcb818ddb33d84ddfc32020900000002e49593ff00 | ||
1 output(s) for total of 34.703563739743 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5e14e4085ab2050a392b09227c97c398af4938082a794b15fd04928be8d7b171 | 34.703563739743 | 8885 of 0 | <15> |
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": 7275,
"vin": [ {
"gen": {
"height": 7215
}
}
],
"vout": [ {
"amount": 34703563739743,
"target": {
"tagged_key": {
"key": "5e14e4085ab2050a392b09227c97c398af4938082a794b15fd04928be8d7b171",
"view_tag": "15"
}
}
}
],
"extra": [ 1, 246, 100, 182, 205, 108, 173, 43, 33, 164, 45, 22, 162, 17, 216, 249, 190, 255, 119, 64, 140, 71, 78, 188, 184, 24, 221, 179, 61, 132, 221, 252, 50, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}