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: 2d59f6b26fcd4c696be426a8dd9f7052dab5cb9300faa36fdbe1ca04c805cac7
Tx prefix hash: 3fc35f7b36c4fbdcff2e9d50078ea3bc41e9d45a33555ef63299a64b1b042114
Tx public key: 871e4e171085ecc75cebdce6515e5a049ce029c0193f4e3f45abfdc9592108c0
| Timestamp: 1780824812 | Timestamp [UTC]: 2026-06-07 09:33:32 | Age [y:d:h:m:s]: 00:001:15:13:15 |
| Block: 7238 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 648 | RingCT/type: yes/0 |
| Extra: 01871e4e171085ecc75cebdce6515e5a049ce029c0193f4e3f45abfdc9592108c0020900000003e49593ff00 | ||
1 output(s) for total of 34.702041360402 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6d575aa45faa4d4059486253db9a407788e8a671a2c94958b5a1f34ea5f01987 | 34.702041360402 | 8914 of 0 | <2a> |
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": 7298,
"vin": [ {
"gen": {
"height": 7238
}
}
],
"vout": [ {
"amount": 34702041360402,
"target": {
"tagged_key": {
"key": "6d575aa45faa4d4059486253db9a407788e8a671a2c94958b5a1f34ea5f01987",
"view_tag": "2a"
}
}
}
],
"extra": [ 1, 135, 30, 78, 23, 16, 133, 236, 199, 92, 235, 220, 230, 81, 94, 90, 4, 156, 224, 41, 192, 25, 63, 78, 63, 69, 171, 253, 201, 89, 33, 8, 192, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}