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: 0a61b30e5d82fc49e85a749fe8a8900f3061456452911e92fea1ed36ede2380d
Tx prefix hash: c845c8c312de69c8d7060f860a4b3b9de7a3c4bba517445b6cb86e05c5ba231a
Tx public key: b92ae127e88cea1706bcb7f33e1b1b9dc42d21c7aa115c323b1bc20f72888754
| Timestamp: 1780691038 | Timestamp [UTC]: 2026-06-05 20:23:58 | Age [y:d:h:m:s]: 00:003:05:11:59 |
| Block: 5700 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2186 | RingCT/type: yes/0 |
| Extra: 01b92ae127e88cea1706bcb7f33e1b1b9dc42d21c7aa115c323b1bc20f72888754020900000001e49593ff00 | ||
1 output(s) for total of 34.803989431544 HMNY
| stealth address | amount | amount idx | tag |
| 00: c9475ce293ab6fffd7c4d2c57e140d6acf801cb15b08d5843483fd7362d5f225 | 34.803989431544 | 7151 of 0 | <90> |
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": 5760,
"vin": [ {
"gen": {
"height": 5700
}
}
],
"vout": [ {
"amount": 34803989431544,
"target": {
"tagged_key": {
"key": "c9475ce293ab6fffd7c4d2c57e140d6acf801cb15b08d5843483fd7362d5f225",
"view_tag": "90"
}
}
}
],
"extra": [ 1, 185, 42, 225, 39, 232, 140, 234, 23, 6, 188, 183, 243, 62, 27, 27, 157, 196, 45, 33, 199, 170, 17, 92, 50, 59, 27, 194, 15, 114, 136, 135, 84, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}