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: f9210a0543144b821fc888926ff017532432b4a5a34532aeab684e0d610bcca1
Tx prefix hash: eb664260fd80978c176621e0cdabb6c98d0f483981000d15df5d285f9e19ad9c
Tx public key: e1a66336a8d9045978384c48fc7a2a448eb09e4f09edbf7e4f06dc025dae3e7a
| Timestamp: 1779721433 | Timestamp [UTC]: 2026-05-25 15:03:53 | Age [y:d:h:m:s]: 00:014:11:45:55 |
| Block: 1765 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6155 | RingCT/type: yes/0 |
| Extra: 01e1a66336a8d9045978384c48fc7a2a448eb09e4f09edbf7e4f06dc025dae3e7a020900000001ba6d17be00 | ||
1 output(s) for total of 35.066190865714 HMNY
| stealth address | amount | amount idx | tag |
| 00: 9a0d0ddaad171c411e2350c6f33ec4cf3e44e22d2e1a9321a15e69454335f4ee | 35.066190865714 | 1948 of 0 | <16> |
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": 1825,
"vin": [ {
"gen": {
"height": 1765
}
}
],
"vout": [ {
"amount": 35066190865714,
"target": {
"tagged_key": {
"key": "9a0d0ddaad171c411e2350c6f33ec4cf3e44e22d2e1a9321a15e69454335f4ee",
"view_tag": "16"
}
}
}
],
"extra": [ 1, 225, 166, 99, 54, 168, 217, 4, 89, 120, 56, 76, 72, 252, 122, 42, 68, 142, 176, 158, 79, 9, 237, 191, 126, 79, 6, 220, 2, 93, 174, 62, 122, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}