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: 6a6827a8b494e4519ef5d9133c3a0f67ca6f9b986ae8298b0a5ece5c0a487e30
Tx prefix hash: b2250ac9a617635c89590717bb61376d4c027f6d8736e2778856bbd0bf353834
Tx public key: 2ca45d63fa5dc941b9f3d7a6e8349aaba57fb086ee72b9d8de26b39cd2ef0c84
| Timestamp: 1780993893 | Timestamp [UTC]: 2026-06-09 08:31:33 | Age [y:d:h:m:s]: 00:000:06:17:22 |
| Block: 8284 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 373 | RingCT/type: yes/0 |
| Extra: 012ca45d63fa5dc941b9f3d7a6e8349aaba57fb086ee72b9d8de26b39cd2ef0c84020900000001e49593ff00 | ||
1 output(s) for total of 34.632876731960 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4e3848032a350774ffa43c84c35d050a8b55cb851fff40c55b73dc77a69ed204 | 34.632876731960 | 10252 of 0 | <7f> |
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": 8344,
"vin": [ {
"gen": {
"height": 8284
}
}
],
"vout": [ {
"amount": 34632876731960,
"target": {
"tagged_key": {
"key": "4e3848032a350774ffa43c84c35d050a8b55cb851fff40c55b73dc77a69ed204",
"view_tag": "7f"
}
}
}
],
"extra": [ 1, 44, 164, 93, 99, 250, 93, 201, 65, 185, 243, 215, 166, 232, 52, 154, 171, 165, 127, 176, 134, 238, 114, 185, 216, 222, 38, 179, 156, 210, 239, 12, 132, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}