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: 0553ade4c40b8b52d4b49ce5bb5495e98bc95c4aa382b48ab6bf5305abb35646
Tx prefix hash: 660ed07aa631a24b57acc3a911e9d73dbe85624ec1d7f310c70fc78ae825c19e
Tx public key: f1dbb9b0bb1cacb630b59407264b153cf4243ec4e6bbd7bf81d62fe122846ce4
| Timestamp: 1779945201 | Timestamp [UTC]: 2026-05-28 05:13:21 | Age [y:d:h:m:s]: 00:011:20:22:36 |
| Block: 3553 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4333 | RingCT/type: yes/0 |
| Extra: 01f1dbb9b0bb1cacb630b59407264b153cf4243ec4e6bbd7bf81d62fe122846ce402090000000426697be300 | ||
1 output(s) for total of 34.946806826855 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4ddd2da116fab9dd3c4494c7217f017aad32c336b0cb84230f7707a35793b478 | 34.946806826855 | 4285 of 0 | <3b> |
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": 3613,
"vin": [ {
"gen": {
"height": 3553
}
}
],
"vout": [ {
"amount": 34946806826855,
"target": {
"tagged_key": {
"key": "4ddd2da116fab9dd3c4494c7217f017aad32c336b0cb84230f7707a35793b478",
"view_tag": "3b"
}
}
}
],
"extra": [ 1, 241, 219, 185, 176, 187, 28, 172, 182, 48, 181, 148, 7, 38, 75, 21, 60, 244, 36, 62, 196, 230, 187, 215, 191, 129, 214, 47, 225, 34, 132, 108, 228, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}