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: 1eedc66cc01baf03969d9581af4f192b7f214d266a613427694c1641c6f30ee8
Tx prefix hash: 623f9a7c180793168b6bfa65fcf05b3ca0e400d6177d14c36095dcb0d7733352
Tx public key: 4e58eb2ebc7c919cb2db0408d2783e8e4def6c11664b0bfc2decaa64d7eae4e3
| Timestamp: 1779899388 | Timestamp [UTC]: 2026-05-27 16:29:48 | Age [y:d:h:m:s]: 00:012:10:20:00 |
| Block: 3127 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4773 | RingCT/type: yes/0 |
| Extra: 014e58eb2ebc7c919cb2db0408d2783e8e4def6c11664b0bfc2decaa64d7eae4e302090000000226697be300 | ||
1 output(s) for total of 34.975213740164 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1b8e20ee666f11e13d0d386facdcd91c5832e573ea15ba80c3488af21c500ee1 | 34.975213740164 | 3737 of 0 | <50> |
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": 3187,
"vin": [ {
"gen": {
"height": 3127
}
}
],
"vout": [ {
"amount": 34975213740164,
"target": {
"tagged_key": {
"key": "1b8e20ee666f11e13d0d386facdcd91c5832e573ea15ba80c3488af21c500ee1",
"view_tag": "50"
}
}
}
],
"extra": [ 1, 78, 88, 235, 46, 188, 124, 145, 156, 178, 219, 4, 8, 210, 120, 62, 142, 77, 239, 108, 17, 102, 75, 11, 252, 45, 236, 170, 100, 215, 234, 228, 227, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}