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: 0fd8f83c4e81e72f5ed9e18bab8a6f62348f3fdf80ffd8276987bdf21e076a23
Tx prefix hash: d0f839a1a25c1d5f872c3d2ed26bd75b83e4acd2928cd1f4ea77d6606be9464d
Tx public key: 4c04242eef6f5a297f3d8c7b3255771fd56da35d0b14d72de739a92874c7105c
| Timestamp: 1779770274 | Timestamp [UTC]: 2026-05-26 04:37:54 | Age [y:d:h:m:s]: 00:022:03:58:20 |
| Block: 2001 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6744 | RingCT/type: yes/0 |
| Extra: 014c04242eef6f5a297f3d8c7b3255771fd56da35d0b14d72de739a92874c7105c02090000000126697be300 | ||
1 output(s) for total of 35.050409908221 HMNY
| stealth address | amount | amount idx | tag |
| 00: fc387e36fb0851c3af41eee79f7a83514efc44af91999f87a9c0c2c22fc3a451 | 35.050409908221 | 2283 of 0 | <01> |
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": 2061,
"vin": [ {
"gen": {
"height": 2001
}
}
],
"vout": [ {
"amount": 35050409908221,
"target": {
"tagged_key": {
"key": "fc387e36fb0851c3af41eee79f7a83514efc44af91999f87a9c0c2c22fc3a451",
"view_tag": "01"
}
}
}
],
"extra": [ 1, 76, 4, 36, 46, 239, 111, 90, 41, 127, 61, 140, 123, 50, 85, 119, 31, 213, 109, 163, 93, 11, 20, 215, 45, 231, 57, 169, 40, 116, 199, 16, 92, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}