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: df6f274075dbdcc294676eb26dec7fc7d16d5446ed35611bfe7d88ec9febd5a7
Tx prefix hash: 5be6873beed3cbac70df2e136dca3561da0c9c42dadabafe761f54447dd17534
Tx public key: 4ed55e47d880e76941b9c245e9354d289419285da6088b5457b84aa8d627db49
| Timestamp: 1779437848 | Timestamp [UTC]: 2026-05-22 08:17:28 | Age [y:d:h:m:s]: 00:018:08:51:35 |
| Block: 176 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 8558 | RingCT/type: yes/0 |
| Extra: 014ed55e47d880e76941b9c245e9354d289419285da6088b5457b84aa8d627db49020900000001a662ed0300 | ||
1 output(s) for total of 35.172629986331 HMNY
| stealth address | amount | amount idx | tag |
| 00: 869b9da796f6b49f2ce89944c1d774af3a5712a3385b3c2c5be02bc5f03aa855 | 35.172629986331 | 172 of 0 | <2b> |
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": 236,
"vin": [ {
"gen": {
"height": 176
}
}
],
"vout": [ {
"amount": 35172629986331,
"target": {
"tagged_key": {
"key": "869b9da796f6b49f2ce89944c1d774af3a5712a3385b3c2c5be02bc5f03aa855",
"view_tag": "2b"
}
}
}
],
"extra": [ 1, 78, 213, 94, 71, 216, 128, 231, 105, 65, 185, 194, 69, 233, 53, 77, 40, 148, 25, 40, 93, 166, 8, 139, 84, 87, 184, 74, 168, 214, 39, 219, 73, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}