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: e07f48388a3b3bf5db8e5811e59da0d3291c03554c8bc7a8db50be71e9508521
Tx prefix hash: 048f4a448b04a2ed659ab17d1c899ec5e7cad7a1097b53c849fa78b8a9d0553e
Tx public key: b2f98cb18c441a36d7a780a54856e47bc404a7c18f5c2eb4f56e66d718683c1d
| Timestamp: 1780693824 | Timestamp [UTC]: 2026-06-05 21:10:24 | Age [y:d:h:m:s]: 00:011:10:51:21 |
| Block: 5902 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2843 | RingCT/type: yes/0 |
| Extra: 01b2f98cb18c441a36d7a780a54856e47bc404a7c18f5c2eb4f56e66d718683c1d020900000001e49593ff00 | ||
1 output(s) for total of 34.790582566637 HMNY
| stealth address | amount | amount idx | tag |
| 00: d5a7d94d81e711676681b020fa04b910a60fce0bd9351595a4141a46e0a46dae | 34.790582566637 | 7363 of 0 | <1d> |
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": 5962,
"vin": [ {
"gen": {
"height": 5902
}
}
],
"vout": [ {
"amount": 34790582566637,
"target": {
"tagged_key": {
"key": "d5a7d94d81e711676681b020fa04b910a60fce0bd9351595a4141a46e0a46dae",
"view_tag": "1d"
}
}
}
],
"extra": [ 1, 178, 249, 140, 177, 140, 68, 26, 54, 215, 167, 128, 165, 72, 86, 228, 123, 196, 4, 167, 193, 143, 92, 46, 180, 245, 110, 102, 215, 24, 104, 60, 29, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}