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: 22e6f96c057c269a0e76abd742522bab2a7cefaf6c9eff5fe4c7668cadaf5b43
Tx prefix hash: eac3d79445b0210fb33b16d8d8cdfb5075e475b6ebdc57d974e7d2ef950a3cba
Tx public key: ef833f6ac73b70f2ba4170b703d5faab8e6c1a1fe20f23688c5121caeec049fc
| Timestamp: 1780690884 | Timestamp [UTC]: 2026-06-05 20:21:24 | Age [y:d:h:m:s]: 00:003:02:57:29 |
| Block: 5692 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2194 | RingCT/type: yes/0 |
| Extra: 01ef833f6ac73b70f2ba4170b703d5faab8e6c1a1fe20f23688c5121caeec049fc020900000001e49593ff00 | ||
1 output(s) for total of 34.804520502836 HMNY
| stealth address | amount | amount idx | tag |
| 00: 56090c5f28f497d39cbfd2e6bb925a4307f9fbb387062e004740993b4e15ef32 | 34.804520502836 | 7143 of 0 | <4f> |
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": 5752,
"vin": [ {
"gen": {
"height": 5692
}
}
],
"vout": [ {
"amount": 34804520502836,
"target": {
"tagged_key": {
"key": "56090c5f28f497d39cbfd2e6bb925a4307f9fbb387062e004740993b4e15ef32",
"view_tag": "4f"
}
}
}
],
"extra": [ 1, 239, 131, 63, 106, 199, 59, 112, 242, 186, 65, 112, 183, 3, 213, 250, 171, 142, 108, 26, 31, 226, 15, 35, 104, 140, 81, 33, 202, 238, 192, 73, 252, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}