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: e204bccd4c6602fc24f35d3930deed1c6dc6db6001f7e8c146bafdd9e8bb56dc
Tx prefix hash: 3be0a4dd6e5baa7e5f2777912e8ea57ed768fff293f2d018d0ea8ad9d1d8fab2
Tx public key: 4c935ae3c803ee7f1bfca4c1dd1530138fa653945f7cdde9b9efece6d064d672
| Timestamp: 1780695415 | Timestamp [UTC]: 2026-06-05 21:36:55 | Age [y:d:h:m:s]: 00:003:05:03:41 |
| Block: 5973 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1923 | RingCT/type: yes/0 |
| Extra: 014c935ae3c803ee7f1bfca4c1dd1530138fa653945f7cdde9b9efece6d064d672020900000002e49593ff00 | ||
1 output(s) for total of 34.785871479467 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8f6ea52aba8669e51a5e8627b832fd9a22ac7c1fd1cc0a99e1ad30cac8056bb3 | 34.785871479467 | 7438 of 0 | <a1> |
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": 6033,
"vin": [ {
"gen": {
"height": 5973
}
}
],
"vout": [ {
"amount": 34785871479467,
"target": {
"tagged_key": {
"key": "8f6ea52aba8669e51a5e8627b832fd9a22ac7c1fd1cc0a99e1ad30cac8056bb3",
"view_tag": "a1"
}
}
}
],
"extra": [ 1, 76, 147, 90, 227, 200, 3, 238, 127, 27, 252, 164, 193, 221, 21, 48, 19, 143, 166, 83, 148, 95, 124, 221, 233, 185, 239, 236, 230, 208, 100, 214, 114, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}