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: bb331248b790403a11bd6265da3f4ee8a26e37c033d1930d92f4e517f69cb7e5
Tx prefix hash: 39eea70f7884db5c85a2c4e3b38c9c04029150cf6a9bafd6a08f3b403306bb1f
Tx public key: f37fbfcbad1ca1c7756e18ea061f70cdb45048f02fc8da88757b55f2f63afd4a
| Timestamp: 1780058419 | Timestamp [UTC]: 2026-05-29 12:40:19 | Age [y:d:h:m:s]: 00:011:04:28:44 |
| Block: 4484 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4250 | RingCT/type: yes/0 |
| Extra: 01f37fbfcbad1ca1c7756e18ea061f70cdb45048f02fc8da88757b55f2f63afd4a02090000000126697be300 | ||
1 output(s) for total of 34.891320135460 HMNY
| stealth address | amount | amount idx | tag |
| 00: 0f73924dfde4be1f3a42fb92531167028681fe3da41bbe1a845d3b6daa74aff0 | 34.891320135460 | 5617 of 0 | <5f> |
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": 4544,
"vin": [ {
"gen": {
"height": 4484
}
}
],
"vout": [ {
"amount": 34891320135460,
"target": {
"tagged_key": {
"key": "0f73924dfde4be1f3a42fb92531167028681fe3da41bbe1a845d3b6daa74aff0",
"view_tag": "5f"
}
}
}
],
"extra": [ 1, 243, 127, 191, 203, 173, 28, 161, 199, 117, 110, 24, 234, 6, 31, 112, 205, 180, 80, 72, 240, 47, 200, 218, 136, 117, 123, 85, 242, 246, 58, 253, 74, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}