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: 428f090fb45d002fc5eb997b0a94fd79f0d05f88b31b85d7593804fa8c051128
Tx prefix hash: f33fbc18f7c3fafd0f5130115a97bcfb992138a0059230c4f00a611a4bde6d53
Tx public key: 7c107bb22bcd1fbab567daa52d2d3da903b855bf7ed9f8c4db8c82de84777890
| Timestamp: 1780989990 | Timestamp [UTC]: 2026-06-09 07:26:30 | Age [y:d:h:m:s]: 00:000:08:33:14 |
| Block: 8207 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 484 | RingCT/type: yes/0 |
| Extra: 017c107bb22bcd1fbab567daa52d2d3da903b855bf7ed9f8c4db8c82de84777890020900000001e49593ff00 | ||
1 output(s) for total of 34.637963497035 HMNY
| stealth address | amount | amount idx | tag |
| 00: 42973b14ade4e6a5fc168c92991805a863ae786384d13ac5c32d05650d844fb8 | 34.637963497035 | 10161 of 0 | <94> |
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": 8267,
"vin": [ {
"gen": {
"height": 8207
}
}
],
"vout": [ {
"amount": 34637963497035,
"target": {
"tagged_key": {
"key": "42973b14ade4e6a5fc168c92991805a863ae786384d13ac5c32d05650d844fb8",
"view_tag": "94"
}
}
}
],
"extra": [ 1, 124, 16, 123, 178, 43, 205, 31, 186, 181, 103, 218, 165, 45, 45, 61, 169, 3, 184, 85, 191, 126, 217, 248, 196, 219, 140, 130, 222, 132, 119, 120, 144, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}