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: 33b344e0d72499410ff497ec1056b47abaec7864946872470072a76efa584501
Tx prefix hash: 8a46e32603261fb2a0ea287c9affcd5edf0fae7212c3f9fd445f648d890c408a
Tx public key: 009af829dd6b8da589e015e07fee3ff14a5905ddcc7894f29adc562aa6f8de9e
| Timestamp: 1779879189 | Timestamp [UTC]: 2026-05-27 10:53:09 | Age [y:d:h:m:s]: 00:012:12:25:44 |
| Block: 2926 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4960 | RingCT/type: yes/0 |
| Extra: 01009af829dd6b8da589e015e07fee3ff14a5905ddcc7894f29adc562aa6f8de9e02090000000226697be300 | ||
1 output(s) for total of 34.988625018726 HMNY
| stealth address | amount | amount idx | tag |
| 00: 38cd104ccb689aba914ecd0d8e7eef202c6f1f1f687fd0d6afc2cc7727db4560 | 34.988625018726 | 3468 of 0 | <a7> |
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": 2986,
"vin": [ {
"gen": {
"height": 2926
}
}
],
"vout": [ {
"amount": 34988625018726,
"target": {
"tagged_key": {
"key": "38cd104ccb689aba914ecd0d8e7eef202c6f1f1f687fd0d6afc2cc7727db4560",
"view_tag": "a7"
}
}
}
],
"extra": [ 1, 0, 154, 248, 41, 221, 107, 141, 165, 137, 224, 21, 224, 127, 238, 63, 241, 74, 89, 5, 221, 204, 120, 148, 242, 154, 220, 86, 42, 166, 248, 222, 158, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}